As a developer of notify I would like to have a clear and concise understanding on how the CICD works. Since we are migrating to helmfile, there is a good opportunity to document the CICD process.
WHY are we building?
Why do we need this?
WHAT are we building?
What does that entail?
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 notify I would like to have a clear and concise understanding on how the CICD works. Since we are migrating to helmfile, there is a good opportunity to document the CICD process.
WHY are we building?
Why do we need this?
WHAT are we building?
What does that entail?
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