Repository navigation
Startup email alerts + live retry countdown - #5
Merged
Merged
Conversation
RetryCountdown read Date.now() once per render and only re-rendered on the deliveries tab's 5s refetch, so the "in Ns" countdown jumped in ~5s steps. Add a 1s interval that updates a local `now`, so it counts down smoothly and feels real-time, decoupled from the data poll. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
When the wake Lambda actually starts the box (the 0→1 transition), it publishes to an SNS topic subscribed by murugu2001@gmail.com — one email per cold start, naming who woke it, so startups can be monitored. - CDK: SNS topic + email subscription (notifyEmail context, default murugu2001@gmail.com) + sns:Publish grant + TOPIC_ARN on the wake Lambda. - Wake Lambda: handler(event) reads the user email from the request body (falls back to JWT claims) and publishes only on the real start; a notify failure never fails the wake. - FE: extract `email` from the Google ID token at login (jwt.emailFromIdToken), store it, and send it in the requestWake() body. Requires a ComputeStack redeploy + a one-time confirmation of the SNS email subscription. Until the FE is deployed, the email falls back to the JWT sub. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…che) Keeps the VPC/AMI/account-ID lookup cache out of git — it regenerates on each synth/deploy and kept resurfacing as an untracked file (and blocking rebases). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
feat: email alert when the box is woken
The wake Lambda publishes to an SNS topic (email subscription) on the real
0→1transition — one email per cold start, naming who woke it, for monitoring.
notifyEmailcontext, defaultmurugu2001@gmail.com) +sns:Publishgrant +TOPIC_ARNon the wake Lambda.handler(event)reads the user email from the request body(falls back to the JWT
sub) and publishes only on the actual start; a notifyfailure never fails the wake.
emailfrom the Google ID token at login (jwt.emailFromIdToken),store it, and send it in the
requestWake()body.cdk.context.json.)fix(web): tick the retry countdown every second
RetryCountdownreadDate.now()once per render and only re-rendered on the 5sdeliveries refetch, so "in Ns" jumped in ~5s steps. A 1s interval now updates it
smoothly, decoupled from the data poll.