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

Ability to specify arbitrary default app #52254

Closed
flash1293 opened this issue Dec 5, 2019 · 2 comments
Closed

Ability to specify arbitrary default app #52254

flash1293 opened this issue Dec 5, 2019 · 2 comments
Labels
enhancement New value added to drive a business result Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@flash1293
Copy link
Contributor

Currently Kibana offers the kibana.defaultAppId setting to specify the default app to load. However this just works for the "core" Kibana apps that are part of the kibana LP app (loaded under the path /app/kibana). AFAIK there is no way to load a different app (different /app/... path) by default without touching the code. When transitioning to the new platform, the kibana app housing multiple actual apps will go away. the kibana.defaultAppId setting should then be able to also load another app (like monitoring or apm) by default (maybe dropping the kibana. prefix of the config key).

@elastic/kibana-platform Is something like this planned already? I tagged platform because this feels like a platform feature, but feel free to change.

@flash1293 flash1293 added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc enhancement New value added to drive a business result labels Dec 5, 2019
@flash1293 flash1293 changed the title Ability to specify default app Ability to specify arbitrary default app Dec 5, 2019
@pablotr9
Copy link

Hi @flash1293, isn't server.defaultRoute used for that purpose?
You can load an app on start by simply setting server.defaultRoute: /app/<app-name>.

@flash1293
Copy link
Contributor Author

flash1293 commented Dec 24, 2019

Hi @pablotr9, I didn’t know about this config key - I looked it up and it got removed in 7.5 in favor of a per-space advanced setting: #44678 Thanks for making me aware!

I think this feature covers all use cases so I will close things issue. The thing remaining is the deprecation of kibana.defaultAppId, but we should track that separately.

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

No branches or pull requests

2 participants