-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[APM] NP migration core.http.createRouter #49238
Comments
ogupte
added
[zube]: Inbox
Team:APM
All issues that need APM UI Team support
v7.6.0
labels
Oct 24, 2019
Pinging @elastic/apm-ui (Team:apm) |
dgieselaar
added
[zube]: In Progress
and removed
[zube]: (7.6) Planned for release
labels
Oct 25, 2019
dgieselaar
added a commit
to dgieselaar/kibana
that referenced
this issue
Nov 21, 2019
Closes elastic#49238. Pass legacy API to NP plugin in order to use internal SO client Fix issues with agent configuration APIs Update tsconfig template for TS optimization Fix typo
dgieselaar
added a commit
that referenced
this issue
Nov 21, 2019
* [APM] Migrate server routes to NP Closes #49238. Pass legacy API to NP plugin in order to use internal SO client Fix issues with agent configuration APIs Update tsconfig template for TS optimization Fix typo * Review feedback * Fix type issues after browser duration changes * Revert changes in getServices due to readability concerns * Review feedback
dgieselaar
added a commit
that referenced
this issue
Nov 25, 2019
* [APM] Migrate server routes to NP Closes #49238. Pass legacy API to NP plugin in order to use internal SO client Fix issues with agent configuration APIs Update tsconfig template for TS optimization Fix typo * Review feedback * Fix type issues after browser duration changes * Revert changes in getServices due to readability concerns * Review feedback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Meta issue: #32894
Migrate from
server.route
to the NP routercore.http.createRouter
. Also route handlers which depend onserver.savedObjects.SavedObjectsClient
can be upgraded to use the SavedObjectsClient from the NP request context (request.getSavedObjectsClient
)See examples of NP router at https://github.com/elastic/kibana/blob/master/src/core/MIGRATION_EXAMPLES.md#3-new-platform-shim-using-new-platform-router.
Ideally we want to use to use option #3 (NP router shim) but we could also inject the legacy router (
server.route
) into the NP router shim (option #2) if necessary.The text was updated successfully, but these errors were encountered: