StorePick Webshop Subscription Cancel

Overview

Subscription Cancel Lambda calls the OSP SUBSCRIPTION STATUS GET API to get status based on the subscription ID. If the status is ACTIVE then a call is made to OSP SUBSCRIPTIONS STATUS PUT API with status as CANCELLED to cancel that subscription. On success action Id is returned, which is used to call OSP SUBSCRIPTION ACTION STATUS GET API, this returns action status as ‘COMPLETED’ on success. Audit details are sent to kafka along with Failed/Success response.

Account Needed

AWS accounts will be required for DEV/SIT/PROD.

References

1. Python Service with infrastructure as code.

2. Unit tests & code coverage at about 90%+

3. Configuration for multiple environments, DEV/SIT/PRD

Document	Ref
Architecture Document	Solution Architecture.
Jira Story	Technical Elaboration - SPDP-7658.
Bitbucket repository	webshop-service-subscription-cancel.

Testing Approach

We will be using a BDD approach where the behaviour will be tested first the code will be developed to match the tested behaviour.

Deployment strategy

The deployment is handled by a jenkins multibranch pipeline,sk-feature. The commit in the develop branch will automatically deploy the application to the aws environments. The release is done by standard process of tagging the release branch, and by building and deploying from the tags. The tag format is sit-v*-<commit> for nonprod and prd-v*-<commit> for the production release. These tags are manually built on jenkins after the change request has been approved. The release branch is merged to the stable master branch after the successful production deployment.

Components

Components

• Subscription Cancel API Lambda -Runbook
• Subscription Cancel API Lambda-infrastructure
• Subscription Cancel API Lambda - codebase

Diagrams

Subscription Cancel Lambda work flow diagram