Delivery

How a commit becomes running code: checks, images, approval, migrations and rollback.

Part of the path: read these pages in order.

1. CI: the checks on every push

   What must pass before code can ship, and why in that order?

2. CD: from main to running tasks

   What happens, job by job, after a merge to main?

3. OIDC: AWS access without stored keys

   How does GitHub Actions get into AWS without a stored access key?

4. Images and scans

   Why build an image once and deploy the same bytes, and what does the scan block?

5. Migrations in a deploy

   When do database migrations run, and what happens if one fails halfway?

6. The two-phase deploy

   Why are infrastructure changes and new code rolled out in two steps?

7. Rollback and the stale-deploy guard

   How do you roll back, and how does CD refuse to deploy an older commit by mistake?

8. Bootstrap a new AWS account

   What must exist before the very first deploy into a brand-new AWS account?