Skip to content

Conversation

@v1v
Copy link
Member

@v1v v1v commented Dec 2, 2025

Motivation/summary

7.17 is not up-to-date with the new beats ysncup integration from main

accessing gh api wihtout auth is flaky

Checklist

For functional changes, consider:

  • Is it observable through the addition of either logging or metrics?
  • Is its use being published in telemetry to enable product improvement?
  • Have system tests been added to avoid regression?

How to test these changes

BRANCH_NAME=7.17 GITHUB_ACTOR=v1v GITHUB_TOKEN=$(gh auth token) updatecli apply --config .ci/updatecli/update-beats.yml --values .ci/updatecli/values.d/scm.yml


+++++++++++
+ PREPARE +
+++++++++++

Loading Pipeline ".ci/updatecli/update-beats.yml"

SCM repository retrieved: 1


++++++++++++++++++
+ AUTO DISCOVERY +
++++++++++++++++++



++++++++++++
+ PIPELINE +
++++++++++++



##############
# BUMP BEATS #
##############

source: source#beats
------------
The shell 🐚 command "/bin/sh /var/folders/t7/ghqdh8cx2g12pwb_w0ncmw900000gn/T/updatecli/bin/f7d4d2320efca004c44c025764b4f40bee4c48d003685eb6c4911111290190e3.sh" ran successfully with the following output:
----
47f485528b1d42b9879402c10c12daf2d86cfa6e
----
✔ shell command executed successfully
[transformers]
✔ Result correctly transformed from "47f485528b1d42b9879402c10c12daf2d86cfa6e" to "47f485528b1d"

condition: condition#is-already-updated
----------------------------
The shell 🐚 command "/bin/sh /var/folders/t7/ghqdh8cx2g12pwb_w0ncmw900000gn/T/updatecli/bin/c00288ed0993e014c2067217f19047aa2c037ca4b055973eb50b962db6dbd91b.sh" ran successfully with the following output:
----
----
✔ shell condition of type "console/output", passing

target: target#beats
------------
The shell 🐚 command "/bin/sh /var/folders/t7/ghqdh8cx2g12pwb_w0ncmw900000gn/T/updatecli/bin/503dfe0771ce3e5a0bc6da789d6cd61f42f5f88715bc7ce7032d5689e494539a.sh" ran successfully with the following output:
----
>> Building apm-server.yml for linux/amd64
>> Building apm-server.docker.yml for linux/amd64
--- Use this commit message: Update to elastic/beats@47f485528b1d
----
⚠ - ran shell command ".ci/scripts/update-beats.sh 47f485528b1d"


ACTIONS
========


Bump beats
  => [updatecli] Update to elastic/beats@47f485528b1d


Pull Request available at:

	https://github.com/elastic/apm-server/pull/19784

Existing GitHub pull request found: https://github.com/elastic/apm-server/pull/19784

=============================

SUMMARY:



⚠ Bump beats:
	Source:
		✔ [beats] Get commit SHA of the latest elastic/beats for branch '7.17'
	Condition:
		✔ [is-already-updated] Is version 'github.com/elastic/beats@47f485528b1d' not updated in 'go.mod'?
	Target:
		⚠ [beats] Update to elastic/beats@47f485528b1d


Run Summary
===========
Pipeline(s) run:
  * Changed:	1
  * Failed:	0
  * Skipped:	0
  * Succeeded:	0
  * Total:	1

One action to follow up:
  * https://github.com/elastic/apm-server/pull/19784

Related issues

@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2025

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@v1v v1v changed the title branch 7.1 updatecli: fix 7.17 when fetching the beats sha commit without gh auth Dec 2, 2025
@v1v v1v requested a review from a team December 3, 2025 14:05
Copy link
Contributor

@fr4nc1sc0-r4m0n fr4nc1sc0-r4m0n left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants