fix: use for_each instead of count in aws_s3_bucket_logging #212
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
Replaced the count with a for_each inside
aws_s3_bucket_logging.default
there's no point in the try since the type is clearly defined as list
why
When the
bucket_name
withinlogging
attribute is dynamically defined, like in the case of referencing a bucket created by terraform for loggingwe get this error
For each can work better in this case and will solve the previous error
references