Fix Terraform pipeline issue after upgrade to 4.0.0 #746
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
added 2 commits
July 9, 2024 23:08
…efinition and s3 cp command
…AWS Organizations
stemons
changed the title
sbkok
approved these changes
Jul 10, 2024
StewartW
approved these changes
Jul 10, 2024
javydekoning
approved these changes
Jul 10, 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.
Why?
Fix terraform pipeline issues after upgrade to 4.0.0. Terraform is not able to upload tf statefile to S3 bucket due to wrong definition of S3 terraform backend
Issue #744, #745
What?
Added encryption properties to terraform S3 backend.
Added permission to codebuild role in the deployment account to read AWS Organizations api
By submitting this pull request, I confirm that you can use, modify, copy, and
redistribute this contribution, under the terms of your choice.