fix: Always send filter
map in replication config
#104
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
Send an empty
filter
map if no (or empty)filter
was specified inreplication_configuration
.(I'm not a Terraform expert so I'm not sure if the way I've done it is the best 😅)
Motivation and Context
In the absence of at least an empty
filter
map if no filter was specified in a rule,terraform apply
gives the following error for multi-destination S3 replication rules. See thisterraform-provider-aws
issue for additional context.Number of distinct destination bucket ARNs cannot exceed 1
Breaking Changes
Does not break backwards compatibility with the current major version.
How Has This Been Tested?
examples/*
projects.S3 bucket with Cross-Region Replication (CRR) enabled
example.s3_bucket
to two replica buckets in the same region (one replication rule without a filter specified).Number of distinct destination bucket ARNs cannot exceed 1
error with unmodified code and successful application with modifications.