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
Workaround issue with missing dynamic mapping in tines package (elastic#12082)
No dynamic mapping was being generated for
tines.audit_log.inputs.inputs.options.*, and this package uses the
tines.audit_log.inputs.inputs.options field directly, without having any
mapping for it or its sub-properties.
The workaround ensures that there is a mapping for
tines.audit_log.inputs.inputs.* that serves for
tines.audit_log.inputs.inputs.options as well as for its subobjects.
The configured dynamic mapping was not being generated due to some issue in
Fleet that we are investigating.
We detected this issue while refactoring field mappings tests in
elastic-package, more about this in elastic/elastic-package#2214[1].
[1]elastic/elastic-package#2214 (comment)
Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
0 commit comments