-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Breaking change] Remove proxyElasticMapsServiceInMaps yml setting #82132
Comments
Pinging @elastic/es-ui (Team:Elasticsearch UI) |
@thomasneirynck Would it be helpful if the Upgrade Assistant notified users that they were using this deprecated setting and linked them to migration docs? |
@cjcenizal actually, that would be a good idea. +1 |
FYI I've updated the |
Hi @thomasneirynck! I'm going to add the |
Pinging @elastic/kibana-gis (Team:Geo) |
Change description
Which release will ship the breaking change?
8.0
Describe the change. How will it manifest to users?
Remove the
map.proxyElasticMapsServiceInMaps
option. See #55611Deployments who were previously using this flag to proxy request to EMS through Kibana (rather than having the user's browser call EMS directly), will no longer work. The map will not display in the Maps-app, SIEM, Uptime, Dashboards or Canvas.
How many users will be affected?
Not known. Kibana does not collect telemetry on this setting. Anecdotally (Discuss, sdh, ...), this seems a rarely used setting.
What can users do to address the change manually?
Use the on-prem version of the Elastic Maps Service, which is a Docker service that resides in the Elastic Docker registry, and install it in an accessible location in their internal network . Then, they will need to update the
kibana.yml
to point to this service. It should be released later in the 7.x cycle.How could we make migration easier with the Upgrade Assistant?
Upgrade Assistant could check if
map.proxyElasticMapsServiceInMaps
is set, and if so, notify the user that it is deprecated and link to the migration docs.Are there any edge cases?
Test Data
Will add link here to on-prem EMS, once it has been released.
Cross links
NA
The text was updated successfully, but these errors were encountered: