[ML] Fixing annotations alias checks#58722
Conversation
|
Pinging @elastic/ml-ui (:ml) |
I think this is actually a sign of another bug, alluded to in "We're likely going to have to make some improvements to how Security handles aliases" in elastic/elasticsearch#52304 (comment). Logically the problem being fixed here should have happened both with security enabled and disabled. /cc @jaymode and @gwbrown to make sure your plans for elastic/elasticsearch#52304 cover this. The discrepancy happened when checking for the existence of an alias by asking if it is an alias of any index:
|
|
@elasticmachine merge upstream |
|
Thanks @droberts195, I'll make sure we have integration tests for those scenarios so that they behave the same. |
49a795c to
a7aedd8
Compare
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
Fixes bug caused by the changing of
ml-annotations-readandml-annotations-writeto hidden indices (elastic/elasticsearch#52423) which made it impossible to create annotations when security is disabled.When calling
indices.existsAliaswe now need to specifyindexandname.