-
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
[Maps] Isolate maps-setting froms maps_legacy #92918
[Maps] Isolate maps-setting froms maps_legacy #92918
Conversation
Pinging @elastic/kibana-gis (Team:Geo) |
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.
LGTM, just a few nits
code review, tested in chrome. Tested map.includeElasticMapsService
, map.tilemap.url
, and map.regionmap
and configurations flowed properly to Maps application, vega maps, and tile map and region map
src/plugins/maps_ems/public/service_settings/service_settings.ts
Outdated
Show resolved
Hide resolved
@@ -107,3 +107,4 @@ pageLoadAssetSize: | |||
osquery: 107090 | |||
fileUpload: 25664 | |||
banners: 17946 | |||
mapsEms: 26072 |
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.
Could mapsLegacy
be reduced since this was broken out?
Running node scripts/build_kibana_platform_plugins.js --update-limits
it looks like mapsLegacy
could be set to 87859
which is 5k above the current size.
@elasticmachine merge upstream |
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.
Kibana App code changes LGTM! I tested it locally and works as it should 👏
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
💔 Backport failed❌ 7.x: Commit could not be cherrypicked due to conflicts To backport manually, check out the target branch and run: |
Creates a new plugins, maps_ems, with `map.*` configs and shared EMS-settings. `maps_legacy` now only supports the `region_map` and `coordinate_map` plugins. # Conflicts: # packages/kbn-optimizer/limits.yml
Closes #76532
Partially addresses #89304
map
configuration and ems-settings in a separate plugin, calledmapsEms
maps_legacy
dependencies to justregion_map
andtile_map
.maps_legacy
now only contains common UX, which is mostly leaflet-based. When removingregion_map
andtile_map
,mapsLegacy
can be removed just as well ([Breaking change] Remove Coordinate map and region map visualizations #81703). Removing these plugins, will also resolve the maps-dependencies onkibana_legacy
Remove kibana_legacy plugin #76905.This PR needs a few follow-on PRs: