Action Required: Amendment to Application Identification

[Pavan-SAP]

Previous Approach

Previously, we identified applications using the provider's globalAccountId and btpAppName. However, this approach had a critical limitation: the globalAccountId in the subscription payload might not belong to the provider, making it impossible to uniquely and reliably identify applications.

Target Solution

We have introduced providerSubaccountId to the CAPApplication specification to address this issue. This identifier is included in the subscription payload (e.g. for saas-registry) and, when combined with btpAppName, provides a unique and accurate way to identify applications.

Migration Plan

With Release v0.28.0, we have now deprecated globalAccountId and would recommend all apps to replace it with providerSubaccountId in the CAPApplication specification.

With Release v0.35.0, the providerSubaccountId in the CAPApplication specification is now mandated.

With Release v0.37.0, we introduce new v1alpha2 apiVersion for the CRDs with which globalAccountId is removed. Our controller only uses this new apiVersion, but all valid resources should automatically get updated to v1alpha2 when touched as usual by K8s.

Warning

Action Required:

The globalAccountId field in the CAPApplication spec is deprecated and will be removed in a future release. Update your CAPApplication resources to use providerSubaccountId instead.

[Pavan-SAP]

Please switch to v1alpha2 asap. This is now available with the latest release.