docs: Correct typo in examples and README #34
Merged
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
ZeroOmar
changed the title
ZeroOmar
changed the title
bryantbiggs
changed the title
bryantbiggs
approved these changes
Dec 10, 2024
bryantbiggs
merged commit 9649166
into
terraform-aws-modules:master
9 of 11 checks passed
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.
Description
Fixed a typo in the example in the
README.mdand theexamples/complete/main.tffiles where theaccess_policy_statementsconditionswas written asconditionMotivation and Context
I was deploying an opensearch domain and didn't see any of my conditions appear in terraform plans. so I reviewed the code and found that the dynamic block
conditionwas looking forstatement.value.conditionsBreaking Changes
None
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request