Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add meta.environment to <env>/name.yml #85

Closed
bodymindarts opened this issue Oct 19, 2016 · 4 comments
Closed

Add meta.environment to <env>/name.yml #85

bodymindarts opened this issue Oct 19, 2016 · 4 comments
Assignees

Comments

@bodymindarts
Copy link

bodymindarts commented Oct 19, 2016

There are some paths in vault that we would like to specify in site/properties.yml that differ only by the 'environment' section of the path.

eg: (( vault "secret/aws/" meta.environment "shield/something:secret" ))

Could the environment name be added to the name.yml file by default on environment creation? I think this could be generally useful.

@geofffranks
Copy link
Contributor

Is meta.vault_prefix sufficient? It's defined in name.yaml

Sent from my iPhone

On Oct 19, 2016, at 5:19 AM, Justin Carter [email protected] wrote:

There are some paths in vault that we would like to specify in site/properties.yml that differ only by the 'environment' section of the path.

eg: `(( vault "secret/aws/" meta.environment "shield/something:secret" ))

Could the environment name be added to the name.yml file by default on environment creation? I think this could be generally useful.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@bodymindarts
Copy link
Author

bodymindarts commented Oct 19, 2016

meta.vault_prefix contains "secret/<site>/<env>/<deployment>" but this is for referencing another deployment in the same environment. Eg we are in bosh-deployments and want to get the provisioning_key from the shield deployment of the same environment.

@jhunt
Copy link
Contributor

jhunt commented Oct 19, 2016

I have also run into this.

Having something like this would be awesome:

meta:
  deployment:
    type: redis
    site: aws
    env: sandbox
  vault_prefix: (( concat "secret/" meta.deployment.site "/" meta.deployment.env "/" meta.deployment.type" ))

Because then I can add something like this to global:

meta:
  cf:
    deployment_name: cf
  cf_vault_prefix: (( concat "secret/"  meta.deployment.site "/" meta.deployment.env "/" meta.cf.deployment_name ))

  creds:
    cf:
      admin: (( vault cf_vault_prefix "/admin:password" ))

@geofffranks
Copy link
Contributor

Sounds good to me. Just wanted to make sure vault_prefix wasn't enough :)

Sent from my iPhone

On Oct 19, 2016, at 8:08 AM, James Hunt [email protected] wrote:

I have also run into this.

Having something like this would be awesome:

meta:
deployment:
type: redis
site: aws
env: sandbox
vault_prefix: (( concat "secret/" meta.deployment.site "/" meta.deployment.env "/" meta.deployment.type" ))
Because then I can add something like this to global:

meta:
cf:
deployment_name: cf
cf_vault_prefix: (( concat "secret/" meta.deployment.site "/" meta.deployment.env "/" meta.cf.deployment_name ))

creds:
cf:
admin: (( vault cf_vault_prefix "/admin:password" ))

You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@jhunt jhunt self-assigned this Oct 29, 2016
@jhunt jhunt closed this as completed in 6da79f3 Oct 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants