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

[randomdevpete]

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.

[randomdevpete]

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.

[randomdevpete]

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.

[randomdevpete]

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.

[randomdevpete]

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.

[randomdevpete]

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.

[randomdevpete]

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.

[randomdevpete]

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.