chore: Promote demo image tags to match current dev :latest (2026-05-27)#955
Open
bjagg wants to merge 1 commit into
Open
chore: Promote demo image tags to match current dev :latest (2026-05-27)#955bjagg wants to merge 1 commit into
bjagg wants to merge 1 commit into
Conversation
Standard outcome of `./scripts/release-demo.sh --apply` after 2026-05-27 demo promotion. 29 demo CFN param files updated; MDR API specifically pins to commit `2db4ab9` (the post-LIF-Initiative#947 / pre-LIF-Initiative#950 squash on main). Stacks deployed during this promotion (in order): 1. SSM params via setup-mdr-api-keys.sh (post-confirm key) 2. release-demo.sh --apply (this commit) 3. demo-lif-mdr-api stack (new task def with POST_CONFIRM secret + Cognito/tenant routing env vars) 4. demo-lif-mdr-cognito stack (LifTeamGroup added, post-confirmation Lambda swapped for the version that calls MDR /tenants/provision, verification email template applied) 4b. SAM mdr-database (Flyway V1.2/V1.3/V1.4 + `flyway repair` step from PR LIF-Initiative#939) — caught and added to the cheatsheet during this promotion because the TL;DR was missing this step 5. release-demo-frontend.sh main --apply (header indicator + friendly display_name + right-pin badge) Co-Authored-By: Claude Opus 4.7 (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.
Summary
Standard outcome of running
./scripts/release-demo.sh --applyafter today's full demo-environment promotion. 29 demo CFN param files updated to pin to the dev:latestimage tags as of 2026-05-27. MDR API specifically targets commit2db4ab9(post-#947 / pre-#950).What was deployed today
setup-mdr-api-keys.sh demo --apply/demo/mdr-api/MdrAuthServiceApiKeyPostConfirm+/demo/mdr-post-confirm/MdrApiKeySSM paramsrelease-demo.sh --applydemo-lif-mdr-apistackmdr-api-demo:7with POST_CONFIRM secret + tenant routing env varsdemo-lif-mdr-cognitostackLifTeamGroup(Precedence 10), swapped post-confirm Lambda body, customized verification emailmdr-database(Flyway)clone_lif_schemafunction now exists;tenant_lif_teamcloned from publicrelease-demo-frontend.sh main --applySmoke tests after promotion
Cheatsheet update
The cheatsheet (
docs/operations/guides/884-demo-promotion-cheatsheet.md, still uncommitted in working tree) had Step 4b missing from the TL;DR. I added it locally. Will commit + share once @bjagg reviews.Follow-up
tenant_eval_promotion_smoketest_tenant. I called/tenants/provisiondirectly during step 4b verification, which cloned demo's public into a stale schema. Harmless but cluttery; tracked separately for cleanup when there's bastion / psql access (no clean API path exists to drop it).🤖 Generated with Claude Code