Skip to content

[8.19] Add ecs@mappings component template to transform destination index template (#223878)#224546

Merged
maxcold merged 1 commit intoelastic:8.19from
maxcold:backport/8.19/pr-223878
Jun 19, 2025
Merged

[8.19] Add ecs@mappings component template to transform destination index template (#223878)#224546
maxcold merged 1 commit intoelastic:8.19from
maxcold:backport/8.19/pr-223878

Conversation

@maxcold
Copy link
Copy Markdown
Contributor

@maxcold maxcold commented Jun 19, 2025

Backport

This will backport the following commits from main to 8.19:

Questions ?

Please refer to the Backport tool documentation

…mplate (elastic#223878)

## Summary

Adding `ecs@mappings` to the index template created by fleet for the
transform destination index template

Closes:
- elastic/security-team#10720

Related discussions:
- https://elastic.slack.com/archives/CJZ9U5G9X/p1749565737961249
-
elastic/elastic-package#1641 (comment)

### Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)

(cherry picked from commit 76fdb46)

# Conflicts:
#	x-pack/platform/plugins/shared/fleet/server/services/epm/elasticsearch/transform/install.ts
#	x-pack/platform/plugins/shared/fleet/server/services/epm/elasticsearch/transform/transforms.test.ts
@maxcold maxcold added the backport This PR is a backport of another PR label Jun 19, 2025
@maxcold maxcold requested a review from kibanamachine as a code owner June 19, 2025 10:42
@maxcold maxcold enabled auto-merge (squash) June 19, 2025 10:42
@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Jun 19, 2025
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/fleet (Team:Fleet)

@maxcold maxcold merged commit 05a1333 into elastic:8.19 Jun 19, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR Team:Fleet Team label for Observability Data Collection Fleet team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants