Cherry-pick #21979 to 7.x: [Packetbeat] Create x-pack magefile #22545
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.
Cherry-pick of PR #21979 to 7.x branch. Original message:
What does this PR do?
This PR modifies the way that x-pack packetbeat builds in order to support the build process used in elastic-agent. I'm not entirely sure if there are any other places required for me to modify in order to have CI run
mage package
from the x-pack directory rather than OSS, but this should be all we need to getelastic-agent
to know how to build packetbeat itself.The
elastic-agent
change and packetbeat modifications for config files for elastic-agent configuration syntax are coming in subsequent PRs.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.