-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fleet] Move mappings from index template to component template #123383
Conversation
@elasticmachine merge upstream |
Pinging @elastic/fleet (Team:Fleet) |
@elasticmachine merge upstream |
x-pack/plugins/fleet/server/services/epm/elasticsearch/template/install.ts
Show resolved
Hide resolved
how can this change be tested? |
…into 121184-mapping-component
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
…#123554) Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Hi @juliaElastic I've added test steps to the PR now 👍 |
…tic#123534) * Timelion rescaling vertical bounds incorrectly on window resize * Update test axis labels data as chart has another scale due to updated padding Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
I'm attempting to view the changes and my browser is having a really hard time. Is this something that could be completed across multiple PRs? 1.3k files changed in a single PR is a lot! |
@hop-dev Looks like something went wrong with a merge and a ton of teams got erroneously pinged for code review. If that's so, would you mind closing this and reopening it in a new PR to avoid hitting a lot of unrelated folks with unnecessary pings? |
No idea what happened sorry about this! |
Summary
Closes #121184.
Moves all mappings to the
@mapping
component template. This means that ever data stream will have the@mapping
component template going forward.We do allow integrations to specify custom mappings, such as APM adds it's own dynamic mapping, so I've had to merge the integration mapping with our base mapping (previously this was done by template inheritance.
Test Steps
In order to test this we need to verify that the computed template remains the same now that we have moved the mapping to the component template.
We also need to verify that any custom mappings set by the package are applied, for example APM enables dynamic mapping
the broad test steps are as follows:
Part 1 (on
main
branch)If you want to skip step 1 here is the computed template for
metrics-apm.app
from the APM integration:metrics-apm.app template
Part 2 (on this feature branch, clean install)