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

Stop using mage:import in custom beats #14162

Merged
merged 3 commits into from
Oct 22, 2019

Conversation

jsoriano
Copy link
Member

mage:import doesn't take into account vendorized dependencies, this is a
problen for custom beats, because by default they have libbeat as a
vendorized dependency. The solution would be to use go modules, but in
the meantime lets remove the use of mage:import from the magefiles
intended to be used by custom beats.

Fix #13998

@jsoriano jsoriano added review :Generator Related to code generators for building custom Beats or modules. [zube]: In Review labels Oct 21, 2019
mage:import doesn't take into account vendorized dependencies, this is a
problen for custom beats, because by default they have libbeat as a
vendorized dependency. The solution would be to use go modules, but in
the meantime lets remove the use of mage:import from the magefiles
intended to be used by custom beats.
@jsoriano jsoriano force-pushed the remove-mage-import-custom-beats branch from af3a16d to 08e3c18 Compare October 21, 2019 14:27
@jsoriano jsoriano added needs_backport PR is waiting to be backported to other branches. v7.4.2 v7.5.0 labels Oct 21, 2019
@fearful-symmetry
Copy link
Contributor

It looks like we're missing a bunch of the test targets, or do we not care about those in the generator beats?

@jsoriano
Copy link
Member Author

It looks like we're missing a bunch of the test targets, or do we not care about those in the generator beats?

I wouldn't care about them. Before using mage:import we didn't have them. Also I wouldn't add targets that we need for python or integration testing, as this will probably be different in other beats. I am going to take a look to the go unit testing targets in any case.

@fearful-symmetry
Copy link
Contributor

It looks like we're still importing build but a lot of the Build and CrossBuild targets are missing. We might want those.

@jsoriano
Copy link
Member Author

It looks like we're still importing build but a lot of the Build and CrossBuild targets are missing. We might want those.

Agree, I will add build and crossBuild.

@jsoriano
Copy link
Member Author

Failing tests happening in filebeat only, not related, merging and backporting this.

@jsoriano jsoriano merged commit af5e812 into elastic:master Oct 22, 2019
@jsoriano
Copy link
Member Author

Thanks @fearful-symmetry for the review!

@jsoriano jsoriano deleted the remove-mage-import-custom-beats branch October 22, 2019 08:26
jsoriano added a commit to jsoriano/beats that referenced this pull request Oct 22, 2019
`mage:import` doesn't take into account vendorized dependencies, this is a
problen for custom beats, because by default they have libbeat as a
vendorized dependency. The solution would be to use go modules, but in
the meantime lets remove the use of `mage:import` from the magefiles
intended to be used by custom beats.

(cherry picked from commit af5e812)
@jsoriano jsoriano removed the needs_backport PR is waiting to be backported to other branches. label Oct 22, 2019
jsoriano added a commit that referenced this pull request Oct 25, 2019
`mage:import` doesn't take into account vendorized dependencies, this is a
problen for custom beats, because by default they have libbeat as a
vendorized dependency. The solution would be to use go modules, but in
the meantime lets remove the use of `mage:import` from the magefiles
intended to be used by custom beats.

(cherry picked from commit af5e812)
jorgemarey pushed a commit to jorgemarey/beats that referenced this pull request Jun 8, 2020
`mage:import` doesn't take into account vendorized dependencies, this is a
problen for custom beats, because by default they have libbeat as a
vendorized dependency. The solution would be to use go modules, but in
the meantime lets remove the use of `mage:import` from the magefiles
intended to be used by custom beats.
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
`mage:import` doesn't take into account vendorized dependencies, this is a
problen for custom beats, because by default they have libbeat as a
vendorized dependency. The solution would be to use go modules, but in
the meantime lets remove the use of `mage:import` from the magefiles
intended to be used by custom beats.

(cherry picked from commit 4001f92)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Generator Related to code generators for building custom Beats or modules. review v7.4.2 v7.5.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

mage:import doesn't use vendored beats on custom beats
2 participants