Configure Stage and Prod Deployment Automation #33
Conversation
This file contains 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
cabutlermit
force-pushed
the
gha-automation
branch
from
4ba3929
to
2ea5b98
Compare
Pull Request Test Coverage Report for Build 8377713735Details
💛 - Coveralls |
Why these changes are being introduced: We are close enough to launch that it's time to start prepping for automated deploys to Stage and Prod. How this addresses that need: * Create stage deploy workflow (from TfCloud outputs from the mitlib-tf-workloads-libraries-website repo) * Create prod deploy workflow (from TfCloud outputs from the mitlib-tf-workloads-libraries-website repo) Side effects of this change: Merging this to `main` will enable automated publishing to Stage and Prod Relevant ticket(s): * https://mitlibraries.atlassian.net/browse/GDT-100
cabutlermit
force-pushed
the
gha-automation
branch
from
2ea5b98
to
48b17b2
Compare
JPrevost
approved these changes
Mar 21, 2024
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.
Purpose and background context
We are close enough to launch that it's time to prepare for automated deploys to Stage and Prod.
How can a reviewer manually see the effects of these changes?
Since these are GitHub Actions, there really isn't a way to do any testing before these are in the
mainbranch of the repository. That said, these files come from templates generated by Terraform and equivalent versions have been fully tested in another CDN-related app (cf-lambda-custom-domain).Includes new or updated dependencies?
NO
Changes expectations for external applications?
NO
What are the relevant tickets?
Developer
Dev CF Lambda@Edge Full Deployworkflow has been run to update CloudFront in Dev1Code Reviewer(s)