-
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] Remove proxyElasticMapsServiceInMaps #116184
[Maps] Remove proxyElasticMapsServiceInMaps #116184
Conversation
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
code review
src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker
Outdated
Show resolved
Hide resolved
@@ -306,5 +290,3 @@ export const MAPS_NEW_VECTOR_LAYER_META_CREATED_BY = 'maps-new-vector-layer'; | |||
export const MAX_DRAWING_SIZE_BYTES = 10485760; // 10MB | |||
|
|||
export const emsWorldLayerId = 'world_countries'; | |||
export const emsRegionLayerId = 'administrative_regions_lvl2'; | |||
export const emsUsaZipLayerId = 'usa_zip_codes'; |
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.
this is unrelated. We removed hardcoded usage of these already when introducing the dynamic suggestEMSLayer
API.
Pinging @elastic/kibana-gis (Team:Geo) |
src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker
Show resolved
Hide resolved
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! tested in firefox and code review
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Test Failures
Metrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
Friendly reminder: Looks like this PR hasn’t been backported yet. |
Summary
Closes #82132
This removes the
map.proxyElasticMapsServiceInMaps
yml setting. This flag allowed administrators to have Kibana act as a proxy to the Elastic Maps Service. The original idea behind this flag was to accommodate flexibility in how admins would setup their networks. E.g. in an airgapped environment, or in a DMZ, they may prefer to only configure outbound internet traffic to EMS for only the Kibana server, rather than all users.With the release of the on-prem Elastic Maps Server, this is much less of a requirement now.
For maintainers
This is a breaking change.