-
Notifications
You must be signed in to change notification settings - Fork 124
[CI] Allow to run each cloud cleanup step independently in DRY_RUN false mode #2581
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
Conversation
Use different DRY_RUN env. vars for each step.
9c15c2b
to
7054f85
Compare
💚 Build Succeeded
History
cc @mrodm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't fully understand this PR 🤔 How would we run each step independently with DRY_RUN false?
Sorry, I did not add that explanation. These changes introduce a new selector in the Buildkite UI, so the user can select which step is going to be run in DRY_RUN mode.
|
Oh ok, I misunderstood, I thought that we were fully deprecating the current variable, but I was missing what was replacing it. Thanks. |
* 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)
Use different DRY_RUN environment variable names for each step to be able to choose which one to enable.