-
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
[Ingest Manager] Rollback changes from #77640 not related to the fix #77806
Conversation
* Doing a try/catch and re-throwing doesn't gain us anything. We already catching the error in the route handler * We have logging for the issue in the existing handler. We also don't pass a logging context to functions
Pinging @elastic/ingest-management (Team:Ingest Management) |
💚 Build SucceededBuild metrics
To update your PR or re-run it, just comment with: |
cc @neptunian |
This looks good but I'm not seeing in #77640 where we check the transform exists before deleting it or catch the the possible delete errors. |
Perhaps I mischaracterized what #77640 does, but it does solve the original issue from what we've seen. I believe this is the check aeade44#diff-f05d5ef07fe6c504f052b00bfbdb63a7 but looking at the final commit https://github.com/elastic/kibana/pull/77640/files it seems that's no longer in This PR doesn't change any behavior. It only deletes the try/catch and log statement from whatever was added. |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
…78197) * Rollback the logger & try/catch changes from #77640 (#77806) * Doing a try/catch and re-throwing doesn't gain us anything. We already catching the error in the route handler * We have logging for the issue in the existing handler. We also don't pass a logging context to functions * Add missing import
Summary
The key to #77640 was adding the leading slash to the paths and checking for the transform before we delete it. Those changes are not affected by this PR.
This rolls back any changes that weren't a part of the resolution and/or aren't consistent with plugin style.
appContextService.getLogger()
vs supplying as a parameter