Fix: force re-upload index.html on every frontend deployment#31
Merged
Fix: force re-upload index.html on every frontend deployment#31
Conversation
TimPolk
approved these changes
Apr 1, 2026
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
2 participants
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.
PATCH was missing from the API Gateway CORS allow_methods, causing the browser's preflight request for PATCH /api/auth/profile to be rejected before reaching Lambda — blocking the bank linking flow at budget generation. Also added PLAID_CLIENT_ID, PLAID_SECRET, PLAID_ENV, BREVO_API_KEY, EMAIL_FROM, and EMAIL_FROM_NAME to the Lambda environment in Terraform, which were present in AWS but missing from the config and would have been wiped on the next terraform apply.
aws s3 sync was skipping index.html because Vite builds produce the same file size between deploys (only the 8-char content hash in the asset filenames changes). This left a stale index.html in S3 referencing JS chunk names that no longer existed, causing a MIME type error that broke the entire app on every deployment.