fix: Fix regression with aws_cloudwatch_log_group resource after upgr… #130
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
…ade of AWS provider 3.0 (terraform-aws-modules#106)
|
Hey @antonbabenko this is just a cherry pick of your commit, can we please merge and release a new version for the TF12 compatibility stream. Many thanks |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
…ade of AWS provider 3.0 (#106)
Description
Just cherry picked your commit for the
4.Xversion.Motivation and Context
Deals with the log group missing wildcard regression for folk who want to upgrade to
provider > 3but are still in TF12Breaking Changes
No
How Has This Been Tested?
Ran
planon my organisation repo and the log-group policy resource correctly ends in:*as it was before.