Skip to content

feat(deploy): Telegram + SNS alert on canary rollback (L221 — 3/5) #285

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cipher813 merged 1 commit into from
May 21, 2026
Merged

feat(deploy): Telegram + SNS alert on canary rollback (L221 — 3/5) #285

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions infrastructure/deploy.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,6 +196,16 @@ if [ "$CANARY_STATUS" != "OK" ] && [ "$CANARY_STATUS" != "SKIPPED" ]; then
--region "$REGION" 2>/dev/null || true
echo " Rolled back to version $PREV_VERSION"
fi
# Independent-channel surveillance per ROADMAP L221 — this exact
# rollback chain fired silently 10 consecutive times across 2 days
# (alpha-engine-data #274 retrospective) before Brian noticed the
# GitHub Actions red-icon. Best-effort; trailing || true never
# overrides the deploy's exit 1.
python3 -m alpha_engine_lib.alerts publish \
--severity error \
--source "alpha-engine-data/infrastructure/deploy.sh" \
--message "Canary rolled back: ${FUNCTION_NAME} canary returned status='${CANARY_STATUS}', live alias reverted v${VERSION}→v${PREV_VERSION}. See CloudWatch /aws/lambda/${FUNCTION_NAME} for payload." \
|| true
exit 1
fi
echo " Canary passed (status=$CANARY_STATUS)"
Expand Down
Loading