You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have found some issues we have to investigate. It seems that elastic-package is importing more fields than expected when using external: ecs, what complicates checking for fields duplication.
Also, fields validator in elastic-package uses only the fields defined in the source files, so it is sometimes not possible to pass both the validation of defined fields, and the validation to avoid duplicated fields. Original idea of the fields importer was to import only fields defined explicitly and not subfields of groups, so it is ok if fields validator only uses the source files.
This is a follow up of #309.
We have found some issues we have to investigate. It seems that elastic-package is importing more fields than expected when using
external: ecs
, what complicates checking for fields duplication.Also, fields validator in
elastic-package
uses only the fields defined in the source files, so it is sometimes not possible to pass both the validation of defined fields, and the validation to avoid duplicated fields. Original idea of the fields importer was to import only fields defined explicitly and not subfields of groups, so it is ok if fields validator only uses the source files.So current plan is going to be:
elastic-package
to import only fields explicitly configured, and not subfields. Don't import ECS fields of type group elastic-package#818The text was updated successfully, but these errors were encountered: