Reduce verbosity when checking if package embeds ECS #1774
Merged
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.
We are logging now
Package does not embed ECS mappingsevery time we check if we should embed ECS mappings because they are referenced in the package.This is not so relevant because the final reason to import ECS schema during validation depends on two other variables at the moment, but it sometimes floods the logs. For example when running the pipeline tests of the Azure package, this line is printed 33 times in a row, and is not deterministic on its own for the actual result.
This change removes this debug log, and when the mappings are effectively considered for fields validation, the possible reasons for importing are printed too.