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

cleanup Http Server config in Legacy platform #41740

Closed
mshustov opened this issue Jul 23, 2019 · 1 comment · Fixed by #42818
Closed

cleanup Http Server config in Legacy platform #41740

mshustov opened this issue Jul 23, 2019 · 1 comment · Fixed by #42818
Labels
Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@mshustov
Copy link
Contributor

mshustov commented Jul 23, 2019

After moving http server to the New Platform we can remove some http-server-related settings from the Legacy platform (ssl, autoListen, etc.). There should be something that gives a hint that now config is handled by New Platform

key: Joi.any().description('This key is handled in the new platform ONLY'),
@mshustov mshustov added Feature:New Platform Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Jul 25, 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