feat: Added delete marker in replication rules #103
Closed
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
Added "delete_marker_replication_status " in replication rules
Motivation and Context
In some cases, delete marker is mandatory in v2 replication scenarios, for example saving data that overlaps.
In v3.50 of AWS provider they added:
resource/aws_s3_bucket: Add the delete_marker_replication_status argument for V2 replication configurations (#19323)
This change only includes a new rule lookup and fallback to null. Also it implies an upgrade to 3.50 provider version.
Breaking Changes
N/A
How Has This Been Tested?
Updated in our infraestructure and changes goes from:
to no change when we add this option.