Skip to content

fix(infra): JARL1188 — detach the /ssr/* behaviour so the VPC origin can be updated - #116

Merged
randomdevpete merged 1 commit into
masterfrom
task-1188-vpc-origin-two-phase-cutover
Aug 30, 2026
Merged

fix(infra): JARL1188 — detach the /ssr/* behaviour so the VPC origin can be updated#116
randomdevpete merged 1 commit into
masterfrom
task-1188-vpc-origin-two-phase-cutover

Conversation

@randomdevpete

Copy link
Copy Markdown
Owner

Phase 1 of two: detach only.

Before merging: confirm JarlSsr sits at UPDATE_ROLLBACK_COMPLETE rather than UPDATE_ROLLBACK_FAILED — a wedged stack fails every later deploy for reasons that look unrelated.

  • Drops the /ssr/* behaviour, so nothing is associated with the VPC origin. /ssr/* then falls through to the distribution's static 404 until phase 2 reattaches it, which is what it effectively serves today.
  • JarlSsr is deliberately unchanged: its synthesized resources and exports are byte-identical to master, differing only by two now-unreferenced Fn::GetStackOutput outputs. The AWS::CloudFront::VpcOrigin itself survives.
  • JarlSsr is ordered after JarlStaticSite so the detach lands first — which also lets the origin repoint master already carries finally apply, since nothing is attached by then.

…can be updated

CloudFront rejects an update to a VPC origin while a distribution is still
associated with it, so the distribution has to let go before the origin can be
repointed. Drop the behaviour and order JarlSsr after JarlStaticSite; a later
deploy attaches it again.

Ticket: 1188
@randomdevpete
randomdevpete merged commit 3e1b2e9 into master Aug 30, 2026
5 checks passed
@randomdevpete
randomdevpete deleted the task-1188-vpc-origin-two-phase-cutover branch August 30, 2026 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant