mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
1022ccdf78
## Summary We're moving to a different vault address/instance when we're on the elastic-wide buildkite infra. While the migration is in progress, we can bridge between using this solution. ✅ Tested the status quo by running the PR pipeline (tests all the loads from `pre-command`) and by using `ci:cloud-deploy` (tests vault writing). 🟠 Tested the new vault provider on this PR: https://github.com/elastic/kibana/pull/171317 The secrets can be accessed, *but they can't be written* (neither by me nor) by the PR pipeline. Change requested here: https://elasticco.atlassian.net/browse/ENGPRD-414 However, this PR can be merged without figuring out write access to secrets, this will work as long as we're on the `kibana-buildkite` infra. --- Closes: https://github.com/elastic/kibana-operations/issues/28 Based on: https://github.com/elastic/kibana/pull/157220 --------- Co-authored-by: Jon <jon@budzenski.me> |
||
|---|---|---|
| .. | ||
| common | ||
| lifecycle | ||
| pipelines | ||
| serverless/create_deploy_tag | ||
| steps | ||
| bootstrap.sh | ||
| build_kibana.sh | ||
| build_kibana_plugins.sh | ||
| download_build_artifacts.sh | ||
| packer_cache.sh | ||
| post_build_kibana.sh | ||
| post_build_kibana_plugins.sh | ||
| saved_object_field_metrics.sh | ||