You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 2, 2018. It is now read-only.
Pipelines should be able to read from Vault for secrets.
For now it's only necessary to look for secrets at a shared Vault. They can be scoped by pipeline-remote/pipeline-name. So for example, if the user has the following defined in a task:
the repo was at github.com/project/app, and the pipeline's name is default, runlet would look for the secret at secret/github.com/project/app/default/app-dev:password. runlet would search in its shared Vault. The client can be configured by using VAULT_ADDR and VAULT_TOKEN.
Pipelines should be able to read from Vault for secrets.
For now it's only necessary to look for secrets at a shared Vault. They can be scoped by
pipeline-remote/pipeline-name. So for example, if the user has the following defined in a task:the repo was at
github.com/project/app, and the pipeline's name isdefault,runletwould look for the secret atsecret/github.com/project/app/default/app-dev:password.runletwould search in its shared Vault. The client can be configured by usingVAULT_ADDRandVAULT_TOKEN.