update to v3 of aws and null providers #29
Closed
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
Drewster727
requested review from
jhosteny and
nitrocode
and removed request for
a team
Merged
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.
what
Update aws and null providers to v3
why
My organization was running into issues recently with regard to VPC endpoint changes outlined here:
terraform-aws-modules/terraform-aws-vpc#445
terraform-aws-modules/terraform-aws-vpc#571
Upgrading to v3 caused no noticeable issues with the module or my vpc resources, but did allow us to upgrade our parent repo provider to v3 (which fixed our issue).