[Breaking change] Remove map.regionmap.* kibana.yml settings

[nreese]

Change description

Which release will ship the breaking change?

8.0

Describe the change. How will it manifest to users?

Remove map.regionmap.* kibana.yml settings. map.regionmap configures vector layers that are used by Region map visualizations and Maps application layers for choropleth maps. The vector layers are static GeoJSON files hosted by external HTTP servers.

Region map visualizations will be removed in 8.0 and thus not effected by the changes. With the introduction of GeoJSON Upload, Maps users should index the vector layers in Elasticsearch and use Elasticsearch as the vector layer source instead of layers provided by map.regionmap.

How many users will be affected?

What can users do to address the change manually?

Existing maps using map.regionmap layers will open but show an error for any layers using map.regionmap configuration. Users can remove the map.regionmap layer and recreate the choropleth layer by using GeoJSON Upload to index their static vector data into Elasticsearch. Users can then create a choropleth layer from the indexed vector data.

How could we make migration easier with the Upgrade Assistant?

It is not possible to use Upgrade Assistant since the migration requires indexing vector layers into elasticsearch.

Are there any edge cases?

Test Data

Provide test data. We can’t build a solution without data to test it against.

Cross links

#81703

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[elasticmachine]

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

[alisonelizabeth]

It is not possible to use Upgrade Assistant since the migration requires indexing vector layers into elasticsearch.

@nreese Would it be helpful to a user if Upgrade Assistant checked for the existence of map.regionmap.* kibana.yml settings, and, if it exists, warn the user that it is deprecated and provide the steps you outlined above on how to resolve it?

[alisonelizabeth]

I'm going to remove the Elasticsearch UI team label. Moving forward, this deprecation should be registered by the plugin owner via the core deprecations service (#94845). 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!