Actions
Enhancement #69946
openCheck for duplicate rule priorities in replication configuration
Status:
Pending Backport
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Tags (freeform):
backport_processed
Merge Commit:
Fixed In:
v20.0.0-575-g2e89cd2268
Released In:
v20.2.0~824
Upkeep Timestamp:
2025-11-01T01:00:34+00:00
Description
When multiple replication rules target the same bucket, the rule with the highest priority should be applied. While this logic is already in place, the configuration does not enforce priority settings, which could lead to confusion. This behavior aligns with AWS's implementation for multiple destination buckets as outlined https://aws.amazon.com/blogs/aws/new-amazon-s3-replication-adds-support-for-multiple-destination-buckets/
Updated by Casey Bodley 11 months ago
- Status changed from New to Pending Backport
Updated by Upkeep Bot 11 months ago
- Copied to Backport #70529: squid: Check for duplicate rule priorities in replication configuration added
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 2e89cd2268a5df0fdfb7159be288c78d187570d0
- Fixed In set to v20.0.0-575-g2e89cd2268a
- Upkeep Timestamp set to 2025-07-08T18:07:31+00:00
Updated by Upkeep Bot 8 months ago
- Fixed In changed from v20.0.0-575-g2e89cd2268a to v20.0.0-575-g2e89cd2268a5
- Upkeep Timestamp changed from 2025-07-08T18:07:31+00:00 to 2025-07-14T15:22:00+00:00
Updated by Upkeep Bot 8 months ago
- Fixed In changed from v20.0.0-575-g2e89cd2268a5 to v20.0.0-575-g2e89cd2268
- Upkeep Timestamp changed from 2025-07-14T15:22:00+00:00 to 2025-07-14T20:46:28+00:00
Updated by Upkeep Bot 4 months ago
- Released In set to v20.2.0~824
- Upkeep Timestamp changed from 2025-07-14T20:46:28+00:00 to 2025-11-01T01:00:34+00:00
Actions