[updatecli] Update to elastic/beats@a58aeebb0ce6

[apmmachine]

What

elastic/beats automatic sync

Changeset

• elastic/beats@a58aeebb0ce6

---

Bump beats

Update to elastic/beats@124d2382f570

ran shell command ".ci/scripts/update-beats.sh 124d2382f570"

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[v1v]

When merged then #11999 is required to be merged and the relevant issue in the infra repo

[v1v]

@elastic/apm-server , any idea what's the reason for the current failures?

So far I see one related to some linting:

• 0175dd6#diff-4e591f117441183672ea6df0d7afd6ee8f03b656ecd7aec71f2d7596b2071727

and another one for some system test failures:

• https://github.com/elastic/apm-server/actions/runs/6782039434/job/18433473301?pr=11940#step:5:804

[mergify]

This pull request is now in conflicts. Could you fix it @apmmachine? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b updatecli_updatecli-update-beats-7.17 upstream/updatecli_updatecli-update-beats-7.17
git merge upstream/7.17
git push upstream updatecli_updatecli-update-beats-7.17