Update infrastructure to use NextJS for frontend #2741
Merged
+20
−224
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.
What are the relevant tickets?
https://github.com/mitodl/hq/issues/5556
Description (What does it do?)
Now that we are ready to use NextJS as the production frontend service we are removing the references to S3 as the asset origin. This also removes the duplicate Fastly service that was being used for testing and extraneous DNS entries.
How can this be tested?
Run a Pulumi preview and verify that the duplicate DNS and Fastly entries will be deleted and the existing Fastly service will point to NextJS