-
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
[core] Support x-pack plugins in new platform #39454
Conversation
Unless Kibana is running as oss-only, the x-pack plugins path is configured in the environment for use in plugin discovery.
Pinging @elastic/kibana-platform |
This comment has been minimized.
This comment has been minimized.
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 with copying the testbed plugin to x-pack and it worked 👍
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
retest |
💔 Build Failed |
💚 Build Succeeded |
* Include x-pack plugin path when appropriate Unless Kibana is running as oss-only, the x-pack plugins path is configured in the environment for use in plugin discovery.
@epixa can you please add a Dev Doc section to the PR for the API changes blog? |
@rayafratkina This isn't relevant to plugin developers as it only pertains to code in the Kibana repo which has already been updated to support the change, so I've switched this to |
Unless Kibana is running as oss-only, the x-pack plugins path is
configured in the environment for use in plugin discovery.
Closes #39447