LGA-3086: Setup CI/CD

[said-moj]

What does this pull request do?

Adds a CI/CD Pipeline using GitHub Actions' workflows

Important

All ingress hosts are only accessible whilst using the Global Protect VPN.

Feature Branch Pipeline

All pushes to any branches, except main, trigger the feature branch pipeline, which performs the following jobs:

Static Analysis:

• Runs Ruff formatting

Testing:

• Runs Pytest
• Outputs results of Pytest in an artefact

Build:

• Runs docker build creating an image with a tag relating to the latest commit sha of the branch.
• Runs docker push pushing the image to the AWS Elastic Container Registry in the laa-access-civil-legal-aid-production namespace.

Deploy Dev:

• Installs or updates a Helm release, named after the branch.
• Requires only the static analysis step to pass.
• This creates a new release for each feature branch, with it's own deployment, service and ingress
• Ingress host is given by: [branch name]-access-cla.cloud-platform.service.gov.uk

Deploy UAT:

• Requires approval by a member of laa-get-access
• Requires the static analysis and testing steps to pass
• Updates the Helm release on the namespace
• Ingress host is: https://access-civil-legal-aid-uat.cloud-platform.service.justice.gov.uk/

Release to staging & production

Once a feature has been merged into main the release pipeline will run, performing the following jobs:

Static Analysis

• Runs Ruff formatting

Testing

• Runs Pytest
• Outputs results of Pytest in an artefact

Build

• Requires both the static analysis and testing steps to pass
• Uses docker to build and push the image to the ECR

Deploy Staging:

• Requires approval by a member of laa-get-access
• Updates the Helm release on the namespace
• Ingress host is: https://access-civil-legal-aid-staging.cloud-platform.service.justice.gov.uk/

Deploy Production:

• Requires approval by a member of laa-get-access
• Updates the Helm release on the namespace
• Ingress host is: https://access-civil-legal-aid.cloud-platform.service.justice.gov.uk/

Clean up dev release

Once a Pull Request has been closed, or merged in main, the 'Clean up' workflow will run. This uninstalls the feature's Helm chart from the dev namespace, removing all deployments, ingresses and pods.

Any other changes that would benefit highlighting?

Adds a Flask app which returns the text "Hello, World!" on the "/" route to test the deployment and ingress works as expected.

Checklist

• Provided JIRA ticket number in the title, e.g. "LGA-152: Sample title"

[Pheonnexx]

LGTM good catch by Jav on somethings!

[digitalali-moj]

Legend.