cds-snc / notification-planning-core

Project planning for GC Notify Core Team
0 stars 0 forks source link

Update Release Documentation with Terraform Release process #104

Open ben851 opened 1 year ago

ben851 commented 1 year ago

Description

As a developer of the Notification-Infrastructure repository, I would like to be able to create multiple small production releases per day so that I can increase velocity while maintaining stability.

WHY are we building?

Terraform can be finicky when doing multiple changes at once in lump sum releases. This is compounded by the fact that what we run in staging may not necessarily be what is run in production (we may run 3 PRs in staging one at a time, but when that's released to production, all three changes are done at once). Small changes are safer, but if we're only releasing once per day, this slows down velocity.

WHAT are we building?

We have created a new release process specific to notification-terraform that acts as a framework for determining if we multiple releases can be done in a day. The documentation must be updated to reflect this new process.

VALUE created by our solution

Increased velocity and stability for the Notify infrastructure.

Acceptance Criteria

Given some context, when (X) action occurs, then (Y) outcome is achieved.

QA Steps