forked from elastic/kibana
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Ops] Use vault kv store when on new Buildkite infra (elastic#174915)
## Summary On the new Buildkite infra, our agents won't have write access to the paths we used to write the deployment information upon deployment. We're allowed to use KV writes if we enable it (https://docs.elastic.dev/ci/using-secrets#using-shared-secrets, enabling PRs below). I've built this in a way that we can enable the feature before the final rollout, and we can clear up the branches once done with the rollout. Cloud deployment works on the old infra as well as the new, tested on this PR and elastic#171317 Enabled by: elastic/ci#2594 & elastic/ci#2553 Part of: elastic/kibana-operations#15 Related: https://elasticco.atlassian.net/browse/ENGPRD-414
- Loading branch information
1 parent
1e99f1b
commit b696a04
Showing
3 changed files
with
47 additions
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters