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 deprecated import/export API out of legacy kibana plugin #67981

Closed
joshdover opened this issue Jun 2, 2020 · 2 comments · Fixed by #69474
Closed

Migrate deprecated import/export API out of legacy kibana plugin #67981

joshdover opened this issue Jun 2, 2020 · 2 comments · Fixed by #69474
Assignees
Labels
Feature:Legacy Removal Issues related to removing legacy Kibana Feature:New Platform Feature:NP Migration Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@joshdover
Copy link
Contributor

Related to removing legacy, we need to migrate the last remaining endpoints in the legacy "kibana" plugin.

@joshdover joshdover added Feature:Legacy Removal Issues related to removing legacy Kibana Feature:New Platform Feature:NP Migration Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Jun 2, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@pgayvallet
Copy link
Contributor

As these endpoints are going to be removed on 8.0 anyway, I think creating a specific legacy_export for it would make sense. That would ease the removal later on.

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

Successfully merging a pull request may close this issue.

3 participants