BYOC layers already support different deployment locations (locationId) so in theory adding new location cdse should be sufficient. However, BYOC layer needs to call metadata/collections service to get location if it is not provided. While this service is central (services.sentinel-hub.com) for all "sentinel-hub" deployments (collection on creodias or mundi also uses services.sentinel-hub.com to fetch collection info), it of course uses different endpoint for cdse deployment. So I had to introduce shServiceUrl (not the best name) which is used to replace hardcoded urls for metadata/collections and configuration endpoints.
Other options that I considered and/or tried
create BYOC_CDAS layer which extends BYOC layer and has fixed locationId and uses appropriate shServiceHostName. While this seems to be the easiest solution, I turned out it requires a lot of changes in eob.
BYOC layers already support different deployment locations (
locationId) so in theory adding new locationcdseshould be sufficient. However, BYOC layer needs to callmetadata/collectionsservice to get location if it is not provided. While this service is central (services.sentinel-hub.com) for all "sentinel-hub" deployments (collection on creodias or mundi also uses services.sentinel-hub.com to fetch collection info), it of course uses different endpoint for cdse deployment. So I had to introduceshServiceUrl(not the best name) which is used to replace hardcoded urls formetadata/collectionsandconfigurationendpoints.Other options that I considered and/or tried
shServiceHostName. While this seems to be the easiest solution, I turned out it requires a lot of changes in eob.