Describe the Problem
If using a connectivity proxy in multi-region mode, clients have to set the SAP-Connectivity-Region-Configuration-Id header with each request; for example, when using destinations that means setting the property URL.headers.SAP-Connectivity-Region-Configuration-Id in the destination.
The connectivity:lite binding now seems to have an (optional?) field region_configuration_id, such as
"region_configuration_id": "cf-eu10-canary”
In Kyma/Kubernetes context, people can inject that attribute into the binding via the usual btp-service-operator binding templating capabilities.
It would be nice if Cloud SDK would recognize this attribute (if present, as fallback if the header is not set).
Propose a Solution
If a destination does not have the according header set, but the used binding does have the region_configuration_id attribute, then use it for the requests sent to the connectivity-proxy endpoint.
Describe Alternatives
No response
Affected Development Phase
Getting Started
Impact
Inconvenience
Timeline
No response
Additional Context
Not a must but could improve the overall usage experience.
Probably also applicable for the Java Cloud SDK.
Describe the Problem
If using a connectivity proxy in multi-region mode, clients have to set the
SAP-Connectivity-Region-Configuration-Idheader with each request; for example, when using destinations that means setting the propertyURL.headers.SAP-Connectivity-Region-Configuration-Idin the destination.The
connectivity:litebinding now seems to have an (optional?) fieldregion_configuration_id, such asIn Kyma/Kubernetes context, people can inject that attribute into the binding via the usual btp-service-operator binding templating capabilities.
It would be nice if Cloud SDK would recognize this attribute (if present, as fallback if the header is not set).
Propose a Solution
If a destination does not have the according header set, but the used binding does have the
region_configuration_idattribute, then use it for the requests sent to the connectivity-proxy endpoint.Describe Alternatives
No response
Affected Development Phase
Getting Started
Impact
Inconvenience
Timeline
No response
Additional Context
Not a must but could improve the overall usage experience.
Probably also applicable for the Java Cloud SDK.