-
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] Remove aliases from index_template when updating an existing template #91200
[Fleet] Remove aliases from index_template when updating an existing template #91200
Conversation
…tall-template-aliases
…tall-template-aliases
Pinging @elastic/fleet (Team:Fleet) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀 🌔
💛 Build succeeded, but was flaky
Test FailuresKibana Pipeline / general / Chrome X-Pack UI Functional Tests.x-pack/test/functional/apps/transform/feature_controls/transform_security·ts.transform feature controls security global dashboard all with transform_user should render the "Data" section with TransformStandard Out
Stack Trace
Metrics [docs]
To update your PR or re-run it, just comment with: |
…template (elastic#91200) # Conflicts: # x-pack/plugins/fleet/server/services/epm/elasticsearch/template/install.test.ts
Description
Reapply #91142
The commit was reverted du to a type issue this fix it c5b5f20
This was merged between the CI and the merge of the previous PR #90492
Context
Resolve #90984
Ensure we aliases from index_template when updating an existing index template
When updating an index template we put new component template before updating the index template, this cause validation error in the case where the index template contains the
aliases
property. That PR ensure the aliases property is removed before.How to test
Start with a Kibana 7.10 setup fleet and endpoint than update to that PR you should be able to upgrade and go to fleet and the index_template for
logs-endpoint*
should not contains aliasesLocally I tested it like this (without the fix I got the issue)
First run kibana from the
7.10
branch,yarn es snapshot --license trial --password changeme -E xpack.security.authc.api_key.enabled=true -E path.data=/tmp/es-data
Than checkout that PR
yarn es snapshot --license trial --password changeme -E xpack.security.authc.api_key.enabled=true -E path.data=/tmp/es-data
Release note
Fix an upgrade issue in Fleet from 7.10 to 7.11 happening with the endpoint package.