-
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
[Component templates] Fix failing API test #94831
[Component templates] Fix failing API test #94831
Conversation
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
This PR will probably fail until the snapshot is promoted with the change. A couple options that come to mind:
|
👍 thanks @tylersmalley! I've skipped the test for now, and can open up a follow-up PR to re-enable. |
Thanks, will merge, kick off a snapshot and report back when it's available. Snapshot verifications: |
* fix failing component templates test * temporarily skip test
* fix failing component templates test * temporarily skip test Co-authored-by: Alison Goryachev <[email protected]>
💔 Build Failed
Failed CI StepsMetrics [docs]
To update your PR or re-run it, just comment with: |
Fixes #94773
The ES team recently merged elastic/elasticsearch#70314, which adds support for deleting multiple component templates. As part of this change, it looks like the error message returned when a component template doesn't exist was changed from
IndexTemplateMissingException
toResourceNotFoundException
(which is more appropriate). This PR updates the expected error message in the test.As a follow-up, we should consider using the updated API rather than making a delete request per component template for bulk deletes. Since this failed test is preventing the promotion of the current Elasticsearch nightly snapshot, I think that enhancement is best addressed separately.