Pinging @elastic/agent (Team:Agent)

This pull request doesn't have a Team:<team> label.

/package

One question: is there a programmatic manner to know that this PR includes all missing Beats and platforms? In other words, are all beats going to be packaged after this PR?

Maybe for a follow-up, I could see the build system returning a list with all beats, so then it's possible to consume that output and verify that in fact all beats where packaged.

At the moment we can only detect issues indirectly if the E2E testing fails. We only have tests to see if the generated package is correct. But I am not aware of anything that checks the list of expected packages. @v1v Maybe it is worth adding an extra job/step to see if all packages are built?

Maybe it is worth adding an extra job/step to see if all packages are built?

I'm not sure how to do this :/ . IIUC, the consumers are the ones that could detect this issue, unless the build system got a specific mage goal to confirm if the generated files for the given beat module matches with the expected ones. Off the top of my head, could the mage build system have some UTs with those particular cases? Other than that, how do you foresee this?

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

💚 Flaky test report

Tests succeeded.