Skip to content
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

Testing Elastic-wide Buildkite system #157220

Closed
wants to merge 33 commits into from

Conversation

brianseeders
Copy link
Contributor

Please ignore

@brianseeders brianseeders added release_note:skip Skip the PR/issue when compiling release notes backport:skip This commit does not require backporting skip-ci kme-test labels May 9, 2023
delanni added a commit that referenced this pull request Dec 6, 2023
…72175)

## 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:
#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: elastic/kibana-operations#28

Based on: #157220

---------

Co-authored-by: Jon <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting kme-test release_note:skip Skip the PR/issue when compiling release notes skip-ci
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants