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 ui/registry/feature_catalogue to New Platform #46738

Closed
joshdover opened this issue Sep 26, 2019 · 1 comment · Fixed by #48818
Closed

Migrate ui/registry/feature_catalogue to New Platform #46738

joshdover opened this issue Sep 26, 2019 · 1 comment · Fixed by #48818
Assignees
Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@joshdover
Copy link
Contributor

joshdover commented Sep 26, 2019

The Kibana app has a "feature catalogue" registry to populate the Directory page at /app/kibana#/home/feature_directory. This is used by all plugins that have UI applications and needs to be migrated. Since this affects so many plugins, the Platform team is planning to take this on in order to unblock migrations.

Some raw thoughts:

  • It seems that the source of truth for this directory could actually be all of the apps registered with the ApplicationService? This won't work because some "features" are sub-applications, such as grokdebugger or rollup.
@joshdover joshdover added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform labels Sep 26, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

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

Successfully merging a pull request may close this issue.

2 participants