Repository navigation
ops: read-only Telegram route check (NOTIFY-01) - #408
Merged
Merged
Conversation
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.
Read-only workflow_dispatch check for the unified notification bot cutover.
Reports per Cloud Run service: traffic split, template revision, recent revisions (Ready, TELEGRAM_TOKEN secret name/version, image, commit-sha label, runtime SA). Checks whether the deploy SA can read each referenced Telegram secret and
quant-sentinel-telegram-bot-token, resolving to public bot id/username via getMe, and lists unconditional accessors on the contract secret when the policy is readable.Never prints token values or chat ids; token is masked. No changes to Cloud Run, secrets, IAM, schedulers or trading. Mirrors CharlesSchwabPlatform notify-route-check (#507/#508).