You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
align the behavior of the region-maps with the maps app and do a simple CORS-call, without injecting the additional kbn-version header.
This also introduces an internal refactor.
layers and tms-services configured in the kibana.yml are no longer proxied through the meta-call.
This also fixes the bug that the initial-layer selection now correctly uses the tilemap.* config from kibana.yml when it is present
Discuss
This changes the default to use CORS (so the flag-config does not conflict with the default (and only behavior) in the region and coordinate map visualizations.
We might want to backport this all the way to 6.7/7.0. For the backports, we would actually want to preserve the default of proxying EMS.
It'd be something like: - 6.7.x: proxy EMS (as it is now) - 7.0.x: proxy EMS (as it is now) - 7.x: use CORS (breaking) - 8.0: use CORS (breaking)
lgtm! Tested locally with custom tile and region map services. My custom maps loaded directly with CORS while EMS services loaded via proxy when map.proxyElasticMapsServiceInMaps: true.
When map.proxyElasticMapsServiceInMaps: false all resources load directly with CORS.
Requests for custom region maps no longer include the kbn-version header which is great!
- breaking change: by default, the Maps app now connects with CORS to EMS. This is optional
- no longer include the kbn-version header when requesting files over CORS in region maps
- breaking change: by default, the Maps app now connects with CORS to EMS. This is optional
- no longer include the kbn-version header when requesting files over CORS in region maps
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #34017
kibana.yml
.Closes #36524
This also introduces an internal refactor.
This also fixes the bug that the initial-layer selection now correctly uses the tilemap.* config from kibana.yml when it is present
Discuss
This changes the default to use CORS (so the flag-config does not conflict with the default (and only behavior) in the region and coordinate map visualizations.We might want to backport this all the way to 6.7/7.0. For the backports, we would actually want to preserve the default of proxying EMS.It'd be something like:- 6.7.x: proxy EMS (as it is now)- 7.0.x: proxy EMS (as it is now)- 7.x: use CORS (breaking)- 8.0: use CORS (breaking)cc @alexfrancoeur