Allow to override ECS objects to group or nested#1493
Merged
jsoriano merged 3 commits intoelastic:mainfrom Oct 6, 2023
Merged
Conversation
Collaborator
💚 Build Succeeded
cc @jsoriano |
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
3 participants
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.
Package Spec v3 is more strict with the validation of objects. They
cannot be used now just to group fields, as is done in ECS.
When it is used only to group fields, the developers needs to decide
if it should be interpreted by Fleet as a
group, so no mapping is installedfor the field itself, but for its subfields, or as a
nested, so the objectis installed as
nested, usually intended for arrays of objects.Needed for elastic/integrations#8115.