[8.17](backport #7186) Speed up serverless Beat tests by not testing Metricbeat or Auditbeat #7257
+0
−10
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.
What does this PR do?
Stops testing Metricbeat and Auditbeat in the serverless Beat tests. The way this step was written it re-invoked the mage integration test target serially 3 times in a row which re-does provisioning unnecessarily. The tests should be rewritten eventually.
These tests also primarily test libbeat setup functionality that is shared amongst Beats, and we already aren't testing all the Beats, so let's just smoke test the one that covers the most functionality.
Why is it important?
These tests take too long.
Related issues
This is an automatic backport of pull request #7186 done by [Mergify](https://mergify.com).