As a developer of GC Notify, I would like the database migration scripts to be automated and reusable so that I don't have to re-write the process for each database upgrade.
WHY are we building?
Why do we need this?
WHAT are we building?
Analyze the existing db upgrade scripts in notification-attic and modify the script and terraform/kubernetes code to be parameterized.
VALUE created by our solution
Close to the business, what's the value?
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Description
As a developer of GC Notify, I would like the database migration scripts to be automated and reusable so that I don't have to re-write the process for each database upgrade.
WHY are we building?
Why do we need this?
WHAT are we building?
VALUE created by our solution
Close to the business, what's the value?
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
Privacy considerations
Security controls in place
Measuring success and metrics
QA Steps