shoc-frontend-new/terraform/live
Adam Moussa c96a259365
Some checks failed
Deploy dev content / Deploy shoc-frontend-new-dev through Terraform (push) Has been cancelled
refactor(cd): ship SPA content from GitHub on main (#220)
* ci(cd): convert SPA hosting to handbook HCP and GitHub content CD

Give HCP the bucket and CloudFront with an empty origin path. GitHub owns
bucket-root sync and invalidation so merge-to-main and a human staging tag
can deploy without creating HCP runs. G13 fails PRs that mix terraform/
with deployable application files.

* ci: run Frontend checks and Terraform CI on PRs to main and dev

Match backend 148 so a PR targeting origin/dev still gets the required
checks. Push remains main only.

* refactor(terraform): keep live/dev and live/staging as HCP roots

Leave the adopted working directories in place so this CD PR does not
retarget two live HCP workspaces. Flattening stays a later change.

* style: prettier terraform-validate.mjs

* fix(terraform): pin githubdeploy assume-role policy in import checker

Reject controlled role updates whose trust document is not the rendered
GitHub OIDC policy, matching the bucket-policy pin.
2026-09-18 14:30:20 -04:00
..
dev refactor(cd): ship SPA content from GitHub on main (#220) 2026-09-18 14:30:20 -04:00
modules refactor(cd): ship SPA content from GitHub on main (#220) 2026-09-18 14:30:20 -04:00
staging refactor(cd): ship SPA content from GitHub on main (#220) 2026-09-18 14:30:20 -04:00
README.md refactor(cd): ship SPA content from GitHub on main (#220) 2026-09-18 14:30:20 -04:00

Live Terraform roots

live/dev/ is the adopted HCP workspace shoc-frontend-new-dev. live/staging/ is shoc-frontend-new-staging (adoption_complete = false).

Do not collapse these into one terraform/ root in the same PR as application CD. Flattening retargets two live HCP working directories and belongs in its own change.