-
-
Notifications
You must be signed in to change notification settings - Fork 371
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
Hashicorp vault as secret storage integration #929
Comments
#915 will allow to set an endpoint for an external secrets provider which could be serving secrets from hashicorp vault. |
That's awesome, thanks folks! |
I've also did some research on this just now and came across the official drone-vault extension. Probably #915 is needed for this in the first place? Here are some additional materials: |
Hi |
Clear and concise description of the problem
Hi there, that would be awesome if secrets would be pullable from Hashicorp Vault, by integration like this
Suggested solution
by this https://docs.gitlab.com/ee/ci/secrets/index.html#configure-your-vault-server
and that https://docs.gitlab.com/ee/ci/secrets/index.html#use-vault-secrets-in-a-ci-job
Alternative
wrapping stuff in bash, that's sad and nasty, because woodpecker does not treat it as concealed string, and secrets gets leaked
import this onto woodpecker plugin system
Additional context
https://www.hashicorp.com/resources/securing-your-ci-pipeline-with-vault
Validations
The text was updated successfully, but these errors were encountered: