5. Deployment

Official deployment branch

Code deployments are made automatically by merging pull requests into the following branches:

• dev
• stating
• master

Overview

Each pull request acceptance to these repositories triggers an event in AWS CodePipeline which automatically fetch, build and deploy the newly merged code in a S3 bucket which serves as a file container by their related AWS CloudFront's endpoints. Some additional layers of Lambdas functions and R53 CNAMEs bound to each CloudFront endpoint, makes them safely available publicly.

Here's an idea of the current deployment workflow for your understanding.

Localhost -> GitHub -> Pull Request -> CodePipeLine -> S3 -> CloudFront -> Lambdas -> R53 (public)

Procedures

ALWAYS CHECKOUT FROM DEV FIRST
git checkout dev

For each tasks:

1. Create a new branch using the following nomenclature (without brackets): [PARENT_BRANCH]-#[ISSUE_ID]-[TASK_NAME]-[ADDITIONAL_COMMENT]
   ex: dev-#47-hide-section-from-homepage.
2. Push changes to branch.
3. Create pull request from branch to dev branch.
4. Ask maintainer to review pull request.
5. Once accepted, review AWS CodePipeline to see if deployment has succeeded. Check logs if any errors.
6. Once builded successfully, invalidate the related CloudFront layer.

CloudFront Invalidation

In Object Paths field, enter the following paths:

/
index.html