[hashicorp_vault] Clarify dynamic mapping for hashicorp_vault.metrics #2994
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?
Remove named mappings and depend on the dynamic mappings. Dynamic mappings
were already present, but elastic-package doesn't honor those during field validation.
So this specifies a
hashicorp_vault.metrics.*.*
mapping for the express purpose of makingelastic-package field validation pass.
Fixes #2898
Checklist
changelog.yml
file.Related issues