Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fix: Always send filter map in replication config #104

Closed
wants to merge 1 commit into from

Conversation

smrz2001
Copy link

@smrz2001 smrz2001 commented Aug 4, 2021

Description

Send an empty filter map if no (or empty) filter was specified in replication_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 this terraform-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?

  • I have tested and validated these changes using one or more of the provided examples/* projects.
  • Tested using the S3 bucket with Cross-Region Replication (CRR) enabled example.
  • Tweaked the example to replicate s3_bucket to two replica buckets in the same region (one replication rule without a filter specified).
  • Observed the Number of distinct destination bucket ARNs cannot exceed 1 error with unmodified code and successful application with modifications.

@smrz2001
Copy link
Author

Hey @antonbabenko, anything I can do to expedite this PR 😄? I can do more work here, if required, just unsure of next steps.

@antonbabenko
Copy link
Member

Hi @smrz2001 !

All good, I will review it and release it during this week. Thank you for the fix!

@smrz2001
Copy link
Author

Hi @smrz2001 !

All good, I will review it and release it during this week. Thank you for the fix!

Thanks so much!!

@antonbabenko
Copy link
Member

I didn't have access to your fork, so I have made #105 instead.

v2.7.0 has been just released.

@smrz2001
Copy link
Author

Oh apologies 😬

Thanks so much for this!

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 28, 2022
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants