Cherry-pick #18086 to 7.x: Fix metricbeat generator test to use mage test#18208
Cherry-pick #18086 to 7.x: Fix metricbeat generator test to use mage test#18208blakerouse merged 1 commit intoelastic:7.xfrom
Conversation
* Use mage unit-test. * Should be make. * Update mage test. * Add PackageKibanaDashboardsFromBuildDir. (cherry picked from commit 9e7321a)
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
💔 Build FailedExpand to view the summary
Build stats
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
|
I think there's a flaw with these tests. It looks like the test generates code from this PR's commit (as it should) but it always pulls in the generated Beat's vendor from "origin/master". |
|
@andrewkroh Yes because of go mods the generated beat always uses |
|
It seems like we need a way to be able to test against the same code that's under test (populate the generated beat's vendor with commit under test). Otherwise you can never be confident that the merged changes are good. Even if we only test on master you'd still have this problem. |
|
@andrewkroh being that issue still affects master, I am going to merge this so 7.x and master are the same in this regard. |
Cherry-pick of PR #18086 to 7.x branch. Original message:
What does this PR do?
Updates the generated custom metricbeat to use
mage testinstead ofmake unit.Why is it important?
So the generator tests pass.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.