Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cherry-pick #7783 to 6.x: X-Pack binaries #8442

Merged
merged 1 commit into from
Sep 27, 2018

Conversation

graphaelli
Copy link
Member

Cherry-pick of PR #7783 to 6.x branch. Original message:

This change brings with-xpack binaries building by doing this:

Introduce x-pack/<beatname>/main.go and its cmd package. These take oss beats RootCmd and inject X-Pack features on it.

The existing magefile.go gains awareness of this and uses it to build and package the x-pack version.

I believe this is the minimal change we would need to just have different binaries. If modules are introduced they will require more packaging changes to take them into account.

This commit implements the necessary logic to build licensed
beats, before that commit, the OSS and the License binaries were
exactly the same.

Changes:

- Added `mage.CrossBuildXPack()` to build the elastic licensed beat.
x-pack/beatname
- Changed the packages.yml to include the artifact from the x-pack
folder.
- Added `mage.UseElasticBeatPackaging()` to build the packages with the new
binaries.
- Added `mage.UseElasticBeatWithoutXPackPackaging()` allow to keep the
previous behavior.
- `make check` and `make fmt` will use the right license for the x-pack
folder.

Co-authored-by: Carlos Pérez-Aradros Herce <[email protected]>
Co-authored-by: Pier-Hugues Pellerin <[email protected]>
(cherry picked from commit bcb0531)
@graphaelli graphaelli merged commit 6d07431 into elastic:6.x Sep 27, 2018
@graphaelli graphaelli deleted the backport_7783_6.x branch September 27, 2018 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants