chore: trigger production report alert deploy#4839
Open
mashbean wants to merge 1 commit into
Open
Conversation
Purpose: - Re-run production deployment after report-alert production infrastructure was prepared. - The report alert code from PR #4830 is already present on master via release PR #4835. - The previous production deploy run 26967814437 failed only at deploy-lambda-production / deploy-report-telegram-alert because report-alert-prod did not exist yet. Prepared infrastructure: - SQS queue: report-alert-prod - SSM: /prod/matters-server/MATTERS_AWS_REPORT_ALERT_QUEUE_URL - SSM: /prod/matters-server/MATTERS_TELEGRAM_BOT_TOKEN - SSM: /prod/matters-server/MATTERS_TELEGRAM_ALERT_CHAT_ID - SSM: /prod/matters-server/MATTERS_OSS_SITE_DOMAIN Acceptance after merge: - Deploy workflow completes successfully for production. - CloudFormation stack report-telegram-alert-production exists and is CREATE_COMPLETE or UPDATE_COMPLETE. - Lambda report-telegram-alert-production is present and mapped to report-alert-prod. - report-alert-prod remains empty after deployment preflight. - Do not run a real production submitReport trigger until explicitly approved. Next-agent instructions: - After this PR is merged, verify the production Deploy workflow first. - If deploy-report-telegram-alert fails, inspect CloudFormation events for report-telegram-alert-production before changing code. - Run only a controlled SQS smoke to report-alert-prod after Lambda deployment succeeds. - Do not send production user reports or create production report rows without human approval.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4839 +/- ##
=======================================
Coverage 72.40% 72.40%
=======================================
Files 1054 1054
Lines 20908 20908
Branches 4515 4515
=======================================
Hits 15139 15139
Misses 5699 5699
Partials 70 70 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This PR is an empty deployment trigger for the production report Telegram alert rollout.
The report-alert code from PR #4830 is already on
masterthrough release PR #4835, but the production Deploy workflow run 26967814437 failed only atdeploy-lambda-production / deploy-report-telegram-alertbecause thereport-alert-prodSQS queue did not exist yet.Prepared infrastructure
report-alert-prodinap-southeast-1./prod/matters-server/MATTERS_AWS_REPORT_ALERT_QUEUE_URL./prod/matters-server/MATTERS_TELEGRAM_BOT_TOKEN./prod/matters-server/MATTERS_TELEGRAM_ALERT_CHAT_ID./prod/matters-server/MATTERS_OSS_SITE_DOMAIN.The Telegram destination intentionally reuses the existing dedicated group
Matters Report Alert Devper rollout decision.Acceptance after merge
deploy-lambda-production / deploy-report-telegram-alertsucceeds.report-telegram-alert-productionis created or updated successfully.reportTelegramAlert.handlerexists and is mapped toreport-alert-prod.report-alert-prodhas no stuck visible, invisible, or delayed messages after preflight.Next-agent instructions
After this PR is merged:
deploy-report-telegram-alertfails, inspect CloudFormation events forreport-telegram-alert-productionbefore changing code.report-alert-prodafter Lambda deployment succeeds.submitReporttrigger or create production report rows without explicit human approval.Notes
This PR intentionally contains no code changes. It exists to let the next production deploy pick up the now-prepared SQS and SSM configuration.