Backport fleet-server#5515#1858
Merged
michel-laterman merged 2 commits intoelastic:8.19from Sep 25, 2025
Merged
Conversation
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
Contributor
|
@michel-laterman I might have led you astray related to backporting (I was thinking about how the beats repo handles release notes instead of this repo) so I went ahead and opened PRs for 8.17 and 8.18: |
colleenmcginnis
approved these changes
Sep 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport elastic/fleet-server#5515 for 8.19.
Add a known-issue for the missing local_metadata.complete mapping.
This issue is still ongoing (even though the attribute has been added to the template) as we have missed updating managed_index_mappings_version, see this discussion.