Move to version 3.x of the AWS Terraform provider #53
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.
🗣 Description
This pull request upgrades the Terraform code to use to version 3 of the Terraform AWS provider.
💭 Motivation and Context
Version 3 of the AWS provider has been out for a while. We don't want to get left behind.
🧪 Testing
terraform-build-user
, I successfully ranterraform apply
and confirmed that thebuild-skeleton-packer
user was properly destroyed and then re-created (there have been some significant Terraform changes since that user was initially created, so this was expected).terraform-post-packer
, I successfully ranterraform apply
in both Staging and Production Terraform workspaces. I then ranterraform destroy
in the Production workspace, since I don't think there's any real Production need for those permissions to theskeleton-packer
AMI (if there is, they can easily be restored later).📷 Screenshots (if appropriate)
🚥 Types of Changes
✅ Checklist