-
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
[Management] Saved objects UI should use the Saved Objects client #19193
[Management] Saved objects UI should use the Saved Objects client #19193
Conversation
To be clear, this isn’t strictly about RBAC. It’s about supporting all of the capabilities that the saved object abstraction provides, like seamless major version upgrades/migrations/pluggability for things like tags/etc. |
💔 Build Failed |
💔 Build Failed |
💚 Build Succeeded |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested that functionality remains the same.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…astic#19193) * Ensure we always go through the saved objects client * Fix a couple UI glitches * Update these tests too * Update snapshots
Backport: 6.x: 7e0e77b |
…ient (elastic#19193)" This reverts commit fcec107.
…ient (elastic#19193) (elastic#19227)" This reverts commit 7e0e77b.
…ient (elastic#19193)" This reverts commit fcec107.
Fixes #19185
#17426 brought in a few poor choices of how to query for saved objects, notably going outside of the saved objects api. This PR addresses that. There should be no functional changes.
cc @kobelb