Add GHA Workflows #3
Merged
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
Why these changes are being introduced: The ECR repositories have been deployed in all three environments in AWS. This updates the app repo with the associated deployment automation workflows. How this addresses that need: * Add the `stage-build` workflow from the mitlib-tf-workloads-ecr repo * Add the `prod-promote` workflow from the mitlib-tf-workloads-ecr repo * Minor formatting changes to the Makefile (to put the Tf-generated header at the top of the file) Side effects of this change: Merges to the `main` branch will now automatically deploy to Stage-Workloads. Tagged releases on the `main` branch will automatically deploy to Prod-Workloads. Relevant ticket(s): * https://mitlibraries.atlassian.net/browse/TIMX-248
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.
Why these changes are being introduced:
The ECR repositories have been deployed in all three environments in AWS. This updates the app repo with the associated deployment automation workflows.
How this addresses that need:
stage-buildworkflow from the mitlib-tf-workloads-ecr repoprod-promoteworkflow from the mitlib-tf-workloads-ecr repoSide effects of this change:
Merges to the
mainbranch will now automatically deploy to Stage-Workloads. Tagged releases on themainbranch will automatically deploy to Prod-Workloads.Relevant ticket(s):