Skip to content

Commit

Permalink
Merge branch 'replatform-adr' into replatform-adrs-proposed
Browse files Browse the repository at this point in the history
  • Loading branch information
tabroughton committed Jan 29, 2024
2 parents 6c95e6e + 3a79781 commit 5ea0d41
Showing 1 changed file with 34 additions and 0 deletions.
34 changes: 34 additions & 0 deletions docs/ADR/ADR004-github-actions-for-cicd-pipeline.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
# ADR004: Github Actions with AWS OIDC provider will be used as the (CI/CD) build, test and deploy pipeline

Date: 2024-01-29

## Status

* Accepted

## Context

* A required CI/CD pipeline for a) build, test and push of docker image, b) management of infra/deployment

## Decision

* Github Actions
- understood well within team and GDS
- many reusable actions
- secure agreement between Github and AWS
- reusable workflows (internal to app)
- Good support from hashicorp/terraform
- [dedicated oidc providers under github/AWS agreement](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services)
- Integrated into PR/Github/etc
- history is maintained even if AWS accounts are removed/recreated
* AWS/Github OIDC provider & role will be set up in each AWS acc using a separate cloudformations which is required to be run independently by SRE/Devops local machine when setting up new AWS accounts

## Considered Options

* Github Actions: decision
* AWS Code Pipeline: requires running pipelines within the env or having separate AWS acc for centralised approach and would require more manual config/set-up to config pipeline, outside of a pipeline.

## Consequences

* required [OIDC provider/role](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services) set up in each AWS acc.

0 comments on commit 5ea0d41

Please sign in to comment.