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.

Sign up for GitHub

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

Jump to bottom

Create compatibility API between legacy xpack_main and licensing plugin #43376

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

Create compatibility API between legacy xpack_main and licensing plugin #43376

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

Comments

@eliperelman
Copy link
Contributor

In order to make migrating between the legacy and current licensing plugin simpler, we either need to create a compatibility layer between the two or consider making API adjustments to new licensing.
@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

@elasticmachine elasticmachine mentioned this issue Aug 16, 2019
Closed
12 tasks
@eliperelman eliperelman mentioned this issue Sep 27, 2019
Closed
7 tasks
@joshdover joshdover mentioned this issue Nov 18, 2019
Merged
3 tasks
@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.

@mshustov mshustov removed the blocker label Nov 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@epixa epixa

Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@epixa @eliperelman @mshustov @elasticmachine