🐛 Redeploy After Nuke Update - Terraform init assume backend role #5761
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
github-actions
bot
added
environments-repository
ASTRobinson
changed the title
davidkelliott
approved these changes
Apr 19, 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.
PR to fix issue ministryofjustice/modernisation-platform#6702
This PR updates the
nuke-redeploy.ymlandterraform-init.shto allow a second variable to be passed in to set thebackend-config. Allowing the job to assume the backend role in the Modernisation Platform account, similar to #4254.I have also updated the
terraform-apply-after-nuke.shscript as this also calls theterraform-initscript however I cannot see anywhere thatterraform-apply-after-nuke.shis being called.