Fix broken yaml test 30_create_from#120662
Merged
parkertimmins merged 4 commits intoelastic:mainfrom Jan 22, 2025
Merged
Conversation
rest spec package name changed but wasn't updated in yaml test
parkertimmins
added
>bug
:Data Management/Indices APIs
elasticsearchmachine
added
the
Team:Data Management (obsolete)
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
Collaborator
|
Hi @parkertimmins, I've created a changelog YAML for you. |
masseyke
approved these changes
Jan 22, 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
3 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.
The rest-api-spec namespace for reindex data stream APIs was changed from
migratetoindicesin #120580 . The yaml testTest create_from with remove_index_blocks set to falseincorrectly uses the old namespace.The bug was introduced in #120643
This fixes the test failure: #120657
The ticket that introduced this bug was backported to 8.x in #120652 . But this bug was caught in CI and the backport failed. So this issue will be fixed backport branch rather than having this fix backported.