[Breaking change] Remove proxyElasticMapsServiceInMaps yml setting

[thomasneirynck]

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 #55611

Deployments 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

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[cjcenizal]

@thomasneirynck Would it be helpful if the Upgrade Assistant notified users that they were using this deprecated setting and linked them to migration docs?

[thomasneirynck]

@cjcenizal actually, that would be a good idea. +1

[alisonelizabeth]

FYI I've updated the How could we make migration easier with the Upgrade Assistant? section in the issue description with CJ's suggestion.

[alisonelizabeth]

Hi @thomasneirynck! I'm going to add the Team:Geo label to this issue. The Upgrade Assistant will no longer be responsible for adding individual deprecation logic. Please consider using the deprecations service (#94845) provided by core to register this deprecation instead. All registered deprecations will be displayed in the Upgrade Assistant (to be implemented via #97159). Feel free to reach out to myself or the core team with any questions!