Product Availability Service¶
Overview¶
This repository contains 1 ECS service for Product Availability Service
Product Availability Service - This service is used to comunicate Availability UI Portal. This service have various endpoint to GET/POST/PUT/DELETE data. This service is mainly used for product import, capping and masking
Accounts Needed¶
AWS accounts will be required for DEV/SIT/PROD.
References¶
Python Flask Service with infrastructure as code.
Document |
Ref |
|---|---|
Architecture Document |
|
Jira Story |
Technical Elaboration - Product Availability Service: SPDP-4473. |
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, https://jenkins.p.morconnect.com/digital/job/aui-osp-productavailability-service/. 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.
Backout¶
To back out we will build off the last release in the master branch and redeploy an old tag version, this shall take around 5 minutes. This will minimise the data loss in case a problem is discovered.
Diagrams¶
Productavailaibility service ** Gives the overview from the productavailability service which contains Ecstask service
Swagger¶
Swagger for application is found in the docs section of the repository.