-
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
[New platform] Expose NP core services and plugins contracts to the legacy server #32468
Conversation
Pinging @elastic/kibana-platform |
* @param kbnServer KbnServer singleton instance. | ||
* @param server Hapi server instance to expose `core` on. | ||
*/ | ||
export function coreMixin(kbnServer: KbnServer, server: Server) { | ||
server.decorate('server', 'core', kbnServer.core); |
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.
to avoid confusion I removed this escape hatch, let me know if we want to keep it and revert the commit
💔 Build Failed |
bfccecf
to
0a5ac14
Compare
💔 Build Failed |
retest |
💚 Build Succeeded |
💚 Build Succeeded |
💔 Build Failed |
still have a problem with build. Feel free to review. If I don't have a solution tomorrow, I will revert the last commit with adding typings for |
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
These changes look good to me, though obviously it needs to pass CI. If it's just a simple type-related change or even a revert of that last type-related push, I don't have to review it again, but let me know if you want me to.
wait for #32578 to address the problem with importing types |
💔 Build Failed |
💚 Build Succeeded |
…egacy server (elastic#32468) * expose NewPlatform core and plugins to legacy server * get rid of .core in favor of .newPlatform * decalre start/stop contract explicitly * expose newPlatform typings * Remove dependency on legacy package_json util from core * Remove dependencies on core/server in core/types
…egacy server (#32468) (#32666) * expose NewPlatform core and plugins to legacy server * get rid of .core in favor of .newPlatform * decalre start/stop contract explicitly * expose newPlatform typings * Remove dependency on legacy package_json util from core * Remove dependencies on core/server in core/types
💔 Build Failed |
💔 Build Failed |
Summary
Issue #32395
Expose New Platform core services and plugins contracts to the legacy server
Functionality is covered in
test:server
Checklist
[ ] This was checked for cross-browser compatibility, including a check against IE11[ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support[ ] Documentation was added for features that require explanation or tutorials[ ] This was checked for keyboard-only and screenreader accessibilityFor maintainers
Dev Docs
Expose New Platform core services and plugins contracts to the legacy server
Kibana is in process of stabilizing of API. During this release, our primary focus was on formalizing API for main core services. Although this is still an experimental API, you can have access to updated elasticsearch and http services on the server side via
kbnServer.newPlatform
that exposes: