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 the Status plugin to the New Platform #51021

Closed
afharo opened this issue Nov 19, 2019 · 2 comments
Closed

Migrate the Status plugin to the New Platform #51021

afharo opened this issue Nov 19, 2019 · 2 comments
Labels
blocker Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0

Comments

@afharo
Copy link
Member

afharo commented Nov 19, 2019

The Status plugin is still running from the legacy code.

Tasks like #49785 would require to update the status but can't do so yet because that would require using the old architecture.

Maybe it can be designed as a status service exposed to each NP Plugin so they can update their own status + the view itself.

@afharo afharo added blocker Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform v8.0.0 labels Nov 19, 2019
@elasticmachine
Copy link
Contributor

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

@afharo
Copy link
Member Author

afharo commented Nov 19, 2019

Duplicate of #41983

@afharo afharo marked this as a duplicate of #41983 Nov 19, 2019
@afharo afharo closed this as completed Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0
Projects
None yet
Development

No branches or pull requests

2 participants