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

[8.13] [CI] Fix issues related to publish (#183393) #183602

Merged
merged 1 commit into from
May 16, 2024

Conversation

delanni
Copy link
Contributor

@delanni delanni commented May 16, 2024

Backport

This will backport the following commits from main to 8.13:

Questions ?

Please refer to the Backport tool documentation

## Summary
On the new infra, the publish step will still require legacy vault
credentials and login.
(https://buildkite.com/elastic/kibana-artifacts-staging/builds/3513#018f7691-73c8-4e6f-862b-328b05d9de3b)

As a fix: this PR digs up the credentials from the vault instead of
gcloud secrets on the new infra.

Also, other usages of role-id/secret-id is used are moved in the
legacy-vault usages, plus minor code re-org, to reduce branching, and
future cleanup.

(cherry picked from commit 05fce3b)

# Conflicts:
#	.buildkite/scripts/steps/serverless/build_and_deploy.sh
@delanni delanni enabled auto-merge (squash) May 16, 2024 08:52
@elasticmachine
Copy link
Contributor

CI was triggered for this PR, but this PR targets 8.13 which should not receive a future release. CI is not supported for these branches. Please consult the release schedule, or contact #kibana-operations if you believe this is an error.

The following branches are currently considered to be open:

  • main
  • 8.14
  • 7.17

@delanni delanni disabled auto-merge May 16, 2024 08:54
@delanni delanni merged commit ace1bbf into elastic:8.13 May 16, 2024
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants