Closed zmoog closed 5 months ago
I validated that it works as expected when this kind of configuration hits the install logic in the fleet kibana plugin and from what I can see it works fine
Does that mean that no code changes are required in Fleet to pick up the subobjects
flag?
@felixbarny
Does that mean that no code changes are required in Fleet to pick up the subobjects flag?
I will validate once that's in, but by my understanding this is the case, yes. The index template mappings object is spread into the "mappings" of the package component template in the fleet code: https://github.com/elastic/kibana/blob/b2add71278992d838fcf5955ff9d6b3e4470274c/x-pack/plugins/fleet/server/services/epm/elasticsearch/template/install.ts#L380
cc @zmoog
What does this PR do?
Add support for
subobjects: false
at the data stream level.Here is an example:
Why is it important?
Give integration developers (per data stream) access to the subobjects option in the integration's index template mappings.
Since we added the
subobjects
option in stack version 8.3, users could customize how Elasticsearch handles fields that contain dots in their names fromtrue
(expanded, current default) tofalse
(not expanded). However, integration developers could not set this up in the integrations.Note on per filed option: the
subobjects
option has been available at the field level since package-spec 3.1.0. However, to make this happen at the data stream level, we needed https://github.com/elastic/elasticsearch/issues/99860 to land in Elasticsearch.Checklist
test/packages
that prove my change is effective.spec/changelog.yml
.Related issues