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

Adds deprecation notice for defaultAppId in favor of defaultRoute #11590

Closed

Conversation

tylersmalley
Copy link
Contributor

@tylersmalley tylersmalley commented May 3, 2017

We have long since replaced the defaultAppId with defaultRoute. This logs a deprecation warning so we can remove in 7.0.

With defaultAppId: discover

[19:50:02.575] [warning][config][deprecation][kibana] Config key "defaultAppId" will be deprecated. Use the equivalent "server.defaultRoute: /app/kibana#/discover"

@tylersmalley tylersmalley added Team:Operations Team label for Operations Team review v5.5.0 v6.0.0 labels May 3, 2017
@tylersmalley
Copy link
Contributor Author

Resolves #6902

@jbudz jbudz self-requested a review May 8, 2017 21:02
Copy link
Member

@jbudz jbudz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One comment below.

Do you have any thoughts on what the removal process for this config will look like? If we visit /app/kibana kibana.defaultAppId is used and defaultRoute won't trigger. Without a defaultAppId in this case we won't load a kibana app. I almost think it makes sense to keep both, and set the defaultRoute to app/kibana#discover to match.

(settings, log) => {
if (has(settings, 'defaultAppId')) {
const newConfig = `server.defaultRoute: /app/kibana#/${get(settings, 'defaultAppId')}`;
log(`Config key "defaultAppId" will be deprecated. Use the equivalent "${newConfig}"`);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thoughts on overriding defaultRoute here to /app/kibana#/${get(settings, 'defaultAppId')}?

(settings, log) => {
if (has(settings, 'defaultAppId')) {
const newConfig = `server.defaultRoute: /app/kibana#/${get(settings, 'defaultAppId')}`;
log(`Config key "defaultAppId" will be deprecated. Use the equivalent "${newConfig}"`);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be "will be removed" right?

@@ -22,9 +22,9 @@ the `server.host` setting. When the value of this setting is `false`, Kibana use
to this Kibana instance.
`kibana.index:`:: *Default: ".kibana"* Kibana uses an index in Elasticsearch to store saved searches, visualizations and
dashboards. Kibana creates a new index if the index doesn’t already exist.
`kibana.defaultAppId:`:: *Default: "discover"* The default application to load.
`kibana.defaultAppId:`:: *Default: "discover"* The default application to load. Use `server.defaultRoute`, as this will be deprecated in future versions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be "will be removed" right?

@spalger spalger added v5.5.0 and removed v5.5.0 labels Jun 6, 2017
Tyler Smalley added 2 commits June 6, 2017 14:52
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
@epixa
Copy link
Contributor

epixa commented Jul 24, 2017

I updated the description to refer to removing this in 7.0 instead of 6.0, since we never got it deprecated.

@tylersmalley
Copy link
Contributor Author

Closing this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
review Team:Operations Team label for Operations Team v7.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants