Fix mappings of flattened fields in azure billing and application insights packages - #6975
Merged
Merged
Conversation
Collaborator
|
/test |
Contributor
Author
|
/test |
1 similar comment
Contributor
Author
|
/test |
kaiyan-sheng
approved these changes
Jul 24, 2023
🌐 Coverage report
|
|
Package azure_application_insights - 1.0.6 containing this change is available at https://epr.elastic.co/search?package=azure_application_insights |
|
Package azure_billing - 1.1.3 containing this change is available at https://epr.elastic.co/search?package=azure_billing |
This was referenced Aug 21, 2023
orestisfl
pushed a commit
to orestisfl/integrations
that referenced
this pull request
May 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Fix mappings of flattened fields in azure billing and application insights packages.
Previous code generates this unexpected mapping:
With this change, this mapping is generated:
We also take the opportunity to increase the format spec version and fix duplicated field definitions.
These issues were identified in elastic/package-spec#527 (comment).
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots