-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Feature: Vault secrets in job specifications #2435
Comments
This is on the roadmap btw and something we are excited about! |
Awesome! |
This would also be helpful for specifying the ssh key used to download git artifacts! |
This came up again on the mailing list recently: https://groups.google.com/d/msg/nomad-tool/W7hSJGBlmlM/6C9swWhqAAAJ |
I guess groundwork has been made in #1765 . It does not support vault secrets yet, but does allow specifying environment variables simiarly to the |
@schmichael can you clarify how #2654 addressed the concern of this mailing list post ? |
I'm a bit confused though. Why does the |
@arianvp Great question! The env var implementation writes environment variables to a file in the alloc directory for a couple reasons:
|
@margueritepd Sorry for the slow update! I posted to the list: https://groups.google.com/d/msg/nomad-tool/W7hSJGBlmlM/E2RLNDFwAgAJ Sadly I was wrong and #2654 didn't address this use case as artifacts are downloaded before templates are rendered. Follow #1185 for arbitrary jobspec templating including vault secrets. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Support of vault secrets would be great for jobs when needing to set passwords in env for docker driver
The text was updated successfully, but these errors were encountered: