Webshop Service Refund BigQuery Publisher¶
Overview¶
This self webshop service refund big query publisher feature is introduced for flowing thru refunds which auto-approved and need approval from contact centre. This solution will provide contact centre team to review self server refund and approve if that fits in their rule. it contains 2 lambda functions to process all the requested data from the osp api and it gives us the data related different refund orders and 2 ecs service which help to maintain the proper flow of the functionality
Webshop Service Refund Big Query Publisher Handler Task¶
Overview¶
This ECS Task will trigger and take the data from the kafka topic which is provided,and we load that data into the big query with combining payload there are two main topic and two tables first topic is for refund approval and second topic is for audit
Account Needed¶
AWS accounts will be required for DEV/SIT/PROD.
References¶
Python Service with infrastructure as code.
Unit tests & code coverage at about 90%+
Configuration for multiple environments, DEV/SIT/PRD
Document |
Ref |
|---|---|
Architecture Document |
|
Jira Story |
|
Bitbucket repository |
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
Diagrams¶
Web Shop Refund Big Query Publisher Diagram