-
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
Remove the es_admin proxy #13000
Remove the es_admin proxy #13000
Conversation
0ebbc8b
to
47f6d82
Compare
d83ae6e
to
b9e8897
Compare
Saved object access is now handled through the saved object client rather than by making direct requests to the admin cluster through a proxy. The indices module and scanner module were both still relying on the proxy, so temporary "legacy" endpoints have been created for their specific use-cases. We should add more purposeful endpoints to the public API in the future to replace these. The admin cluster itself is still readily available on the server and should still be used for all requests for internal kibana indices.
I think a green build is blocked by #13014, or at least I can't get further in the tests than the issue that PR is fixing, but it should be good for review otherwise. |
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 - set pageSize to 1 to functionally test continue.
Merged master since #13014 went in |
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
The angular service was removed in #13000
…3449) The angular service was removed in elastic#13000
…3449) The angular service was removed in elastic#13000
Saved object access is now handled through the saved object client
rather than by making direct requests to the admin cluster through a
proxy. The indices module and scanner module were both still relying on
the proxy, so temporary "legacy" endpoints have been created for their
specific use-cases. We should add more purposeful endpoints to the
public API in the future to replace these.
The admin cluster itself is still readily available on the server and
should still be used for all requests for internal kibana indices.