-
Spike
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
False
-
-
False
-
subs-swatch-lightning
-
-
We've discovered a limitation in how subscription sync handles different cloud providers that's preventing us from testing a critical workflow.
The subscription sync service (SubscriptionSyncService) currently only supports processing subscriptions with external references for AWS Marketplace (awsMarketplace) or IBM Marketplace (ibmmarketplace). This is visible in the SubscriptionDtoUtil.extractBillingProviderId() method, which only looks for these two keys in the subscription's external references map.
When we receive a subscription message via UMB that includes Azure external references, the system doesn't recognize or process them properly. This means Azure subscriptions can only be synced through the contract sync flow (partner API), not through the standard UMB subscription message flow.
This limitation is blocking the implementation of test plan "subscriptions-creation-TC003 - Process UMB subscription with Azure external references", which was designed to verify that Azure subscriptions are handled correctly when received via UMB messages. A component test for this scenario exists but has been disabled since SWATCH-4221.
We need to determine whether this limitation is by design (meaning Azure subscriptions are intentionally only processed via contract sync) or if it's a gap that should be addressed.
Acceptance Criteria
- Investigate how Azure subscriptions are currently processed in the system (I assume it's exclusively via contract sync through the partner API, but this needs verification)
- Determine if this AWS/IBM-only approach in the subscription sync is intentional or a limitation that needs to be fixed
- If this is by design: Delete the blocked test plan "subscriptions-creation-TC003 - Process UMB subscription with Azure external references" and remove the disabled component test that was created for
SWATCH-4221 - If this is a gap: Create a feature request ticket to add Azure billing provider support to the subscription sync flow, including proper handling of Azure external references in SubscriptionDtoUtil
- is triggered by
-
SWATCH-4221 Swatch-Contracts: Test subscription management via messaging broker
-
- Closed
-