Skip to content
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

Migrate away from legacy xpack_main to new licensing plugin #43378

Closed
eliperelman opened this issue Aug 15, 2019 · 2 comments
Closed

Migrate away from legacy xpack_main to new licensing plugin #43378

eliperelman opened this issue Aug 15, 2019 · 2 comments
Assignees
Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@eliperelman
Copy link
Contributor

Once the server and public portions of the new licensing plugin are done and compatible, we should remove the xpack_main bits and ensure consumers are migrated to the new licensing plugin.

@eliperelman eliperelman added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform labels Aug 15, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

@mshustov
Copy link
Contributor

The new platform licensing plugin is not compatible with xpack_main. We are planning to keep both until all plugins migrate from legacy licensing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

4 participants