Skip to content

Conversation

@v1v
Copy link
Member

@v1v v1v commented May 5, 2025

What

  • Use GCP OIDC to copy the logs to the private storage.
  • Use gcloud instead of gsutil (so it honours the Env variables)
  • Tear-down is now managed by the BK plugin itself.

Test

See

image
@v1v v1v mentioned this pull request May 6, 2025
@v1v v1v self-assigned this May 7, 2025
@v1v v1v marked this pull request as ready for review May 7, 2025 07:24
@v1v v1v requested a review from a team as a code owner May 7, 2025 07:24
@v1v v1v requested review from a team May 7, 2025 07:24
Copy link
Contributor

@mrodm mrodm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

cc @v1v

@v1v v1v merged commit dba8f6d into main May 7, 2025
3 checks passed
@v1v v1v deleted the feature/gcp-oidc branch May 7, 2025 16:38
v1v added a commit to v1v/elastic-package that referenced this pull request May 8, 2025
* main: chore: [updatecli] Update latest snapshot to 9.1.0-4348ed5d (elastic#2582) [CI] Allow to run each cloud cleanup step independently in DRY_RUN false mode (elastic#2581) buildkite: use GCP OIDC (elastic#2569) Replace archiver dependency (elastic#2564) github-action: add catalog-validate for GitHub actions (elastic#2576) chore: [updatecli] Update latest snapshot to 9.1.0-62329fee (elastic#2580) Chore(deps): bump golang.org/x/tools from 0.32.0 to 0.33.0 (elastic#2577) Chore(deps): bump gotest.tools/gotestsum from 1.12.1 to 1.12.2 (elastic#2578)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants