-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Stop using mage:import in custom beats #14162
Conversation
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.
af3a16d
to
08e3c18
Compare
It looks like we're missing a bunch of the |
I wouldn't care about them. Before using |
It looks like we're still importing |
Agree, I will add |
Failing tests happening in filebeat only, not related, merging and backporting this. |
Thanks @fearful-symmetry for the review! |
`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)
`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)
`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.
`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)
mage:import
doesn't take into account vendorized dependencies, this is aproblen 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 magefilesintended to be used by custom beats.
Fix #13998