wordpress-fargate: update modules and providers #30
Conversation
This file contains hidden or 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
Author
|
@sunilkumarmohanty When you get a chance, could you please take a look at this PR as well as #31, #32, and #33? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request is one of several changes I made in the course of adapting the wordpress-fargate recipe to my own use. I decided to break up the changes by topic area to make reviewing them more manageable. This PR is the first of four.
This change is mostly housekeeping. I've updated the terraform providers and modules to ensure that we use their latest major releases. The module updates required some minor code changes, and I've set the minimum version for the aws provider to 3.38.0 in order to take advantage of the newly-introduced default_tags feature, which defines a default set of tags for all AWS resources in one shot, rather than having to apply them to each resource individually.