-
Notifications
You must be signed in to change notification settings - Fork 25.1k
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
Use VAULT_TOKEN environment variable if it exists #45525
Conversation
Signed-off-by: Mark Vieira <[email protected]>
Pinging @elastic/es-core-infra |
|
@mark-vieira that issue number looks incorrect. |
Thanks, Alpar. I updated that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
thanks, I had to do this in my fork too. Was planning to send a patch but I was too slow. lgtm |
It's actually elasticsearch/infra#13907 that needs to be addressed before this. Right now this PR wouldn't actually do anything since we never set |
It won't so much but it's a step forward down the right direction. I could also use it in my Zuul tests. I had to hack it in myself but I'd rather use this patch. |
# Conflicts: # .ci/init.gradle
(cherry picked from commit b57f2ff)
There seems to be consensus this is worth happening so I've merged this and backported to all active branches. |
As a follow up to https://github.com/elastic/infra/pull/13780#issuecomment-521025910 we should try and use the
VAULT_TOKEN
passed into the build from CI when possible.