-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Changes rewriteBasePath
core config deprecation level to warning
#114566
Changes rewriteBasePath
core config deprecation level to warning
#114566
Conversation
@elasticmachine merge upstream |
@@ -16,6 +16,7 @@ const rewriteBasePathDeprecation: ConfigDeprecation = (settings, fromPath, addDe | |||
'will expect that all requests start with server.basePath rather than expecting you to rewrite ' + | |||
'the requests in your reverse proxy. Set server.rewriteBasePath to false to preserve the ' + | |||
'current behavior and silence this warning.', | |||
level: 'warning', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed the level to warning for this deprecation to help with cleaning up UA. We need to do some research before deciding on an approach for fully handling the deprecation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Self review
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-core (Team:Core) |
…lastic#114566) Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
💚 Backport successful
This backport PR will be merged automatically after passing CI. |
I'm getting recurring issues with types in the backport PR. I opened new PR directly to 7.x to make the change rather than try to force the backport to work. |
Part of #103915
This PR changes the core
rewriteBasePath
deprecation level fromcritical
towarning
as a stop gap until we come to a decision on an approach.I think it's worth getting this change in to 7.16 to help with reducing noise in the Upgrade Assistant.
Unless anyone feels otherwise, the risk seems quite small.
For maintainers