Repository navigation
Remove gamma.onehook.club frontend site (prod + local stay on gamma backend) - #2
Merged
Merged
Conversation
…cal on gamma backend Keep only local dev and production (onehook.club) as frontend targets. The gamma.onehook.club website, its CDK-managed hosted zone, and the cross-account API DNS delegation are removed. Production and local both continue to point at the Gamma backend (api.gamma.onehook.club) via VITE_BACKEND_STAGE=gamma. - frontend-app.ts: prod-only stage; --context env accepts only 'prod' - frontend-stack.ts: drop apiDelegation + createHostedZone (always import zone) - constants.ts: drop gamma domain, GAMMA_CERTIFICATE_ARN, BACKEND_DNS, DNS_DELEGATION, resolveBackendDns - pipeline: remove DeployGamma + SmokeGamma stages; delete gamma-deploy.yml buildspec - delete unused infra/lambda/api-dns-reader - package.json: drop synth:gamma / deploy:gamma - tests: update pipeline stage expectations and ownership constants - docs: update README + FRONTEND_PRODUCTION for prod-only site Pipeline flow is now: Source -> Verify -> BuildProduction -> ApproveProduction -> DeployProduction -> SmokeProduction.
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
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
Keep only local dev and production (
onehook.club) as frontend targets. Removes thegamma.onehook.clubwebsite deployment, its CDK-managed hosted zone, and the cross-account API DNS delegation. Production and local both continue to point at the Gamma backend (api.gamma.onehook.club) viaVITE_BACKEND_STAGE=gamma.Changes
frontend-app.ts: prod-only stage;--context envaccepts onlyprodfrontend-stack.ts: dropapiDelegation+createHostedZone(always import existing zone)constants.ts: drop gamma domain,GAMMA_CERTIFICATE_ARN,BACKEND_DNS,DNS_DELEGATION,resolveBackendDnsDeployGamma+SmokeGammastages; deletegamma-deploy.ymlinfra/lambda/api-dns-readerpackage.json: dropsynth:gamma/deploy:gammaNew pipeline flow:
Source -> Verify -> BuildProduction -> ApproveProduction -> DeployProduction -> SmokeProduction.Tested
npm run lintclean;npm test228/228 passnpm run synth:prod-> onlyOneHook-Certificate-prod+OneHook-Frontend-prodnpm run synth:pipeline-> 6 correct stages, no gamma site refsOneHook-Frontend-Pipelinedeployed (UPDATE_COMPLETE);get-pipelineconfirms the six stages and removal of the gamma CodeBuild projects/roles/log groups. This PR brings the repo source-of-truth in line with the deployed pipeline.