[8.19] Align beats-bump automation config#6730
Open
jeniawhite wants to merge 1 commit into
Open
Conversation
Switch the updatecli beats config to the file-edit-only form used by the bump-beats-version.yml workflow so the update-beats (8.19) job stops failing at config load. - .ci/updatecli/updatecli.d/update-beats.yml: use BRANCH_NAME / --commit=false config (the old config used requiredEnv GIT_BRANCH + scms/actions, which the new workflow does not set). - updatecli.yml: remove beats from the matrices (now owned by the dedicated workflow). This is the config-only fix for the failing job. The actual elastic/beats bump on 8.19 is left to the automation; note it will pull elastic-agent-libs v0.43.1, which removes the global observer logging API (logp.ToObserverOutput / logp.ObserverLogs) still used in 8.19 test code, so that bump PR will need a separate logptest migration. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Switch the updatecli beats config on
8.19to the file-edit-only form used by thebump-beats-version.ymlworkflow, so theupdate-beats (8.19)job stops failing at config load.Why
The
update-beatsworkflow (onmain) checks out each active branch and runsupdatecli apply --config .ci/updatecli/updatecli.d/update-beats.yml. That config is read from the checked-out branch, but8.19still had the old config (requiredEnv "GIT_BRANCH"+scms/actions), while the new workflow setsBRANCH_NAMEand runs--commit=false:How
.ci/updatecli/updatecli.d/update-beats.yml: replace with theBRANCH_NAME/--commit=falseconfig the new workflow expects..github/workflows/updatecli.yml: removebeatsfrom the matrices (now owned by the dedicated workflow).Scope note (deliberately config-only)
This PR does not include the
elastic/beatsversion bump. Unlike9.3/9.4, bumping beats on8.19pullselastic-agent-libsup tov0.43.1, which removes the global observer logging API (logp.ToObserverOutput/logp.ObserverLogs()) still used across ~22 sites in 6 test files on8.19. That requires backporting thelogptest.NewTestingLoggerWithObservermigration (already done on9.3/main) and is best handled as a separate, deliberate change. With this config fix in place, the automation can run; the resulting bump PR will need that migration before it goes green.🤖 Generated with Claude Code