-
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
[Fleet] Move to ISavedObjectsRepository for Saved Object access #121824
[Fleet] Move to ISavedObjectsRepository for Saved Object access #121824
Conversation
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.
Looking great, thanks for doing this cleanup. It simplifies what we need to think about and eliminates several potential bugs for consumers of Fleet's plugin APIs
x-pack/plugins/fleet/server/services/epm/kibana/assets/install.ts
Outdated
Show resolved
Hide resolved
171de21
to
fe23fd0
Compare
Pinging @elastic/fleet (Team:Fleet) |
e93f5b3
to
c3f8a6c
Compare
c3f8a6c
to
3f9c46b
Compare
Pinging @elastic/apm-ui (Team:apm) |
💔 Build FailedFailed CI StepsTest Failures
Metrics [docs]Unknown metric groupsESLint disabled in files
ESLint disabled line counts
References to deprecated APIs
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @hop-dev |
Summary
As of #120517 we no longer use the functionality of the spaces or security wrapper in the SavedObjectsClient, this means that we are able to move to using the ISavedObjectsRepository interface for accessing saved objects across the board.
This offers two main benefits:
A high level list of the changes I have made: