-
Notifications
You must be signed in to change notification settings - Fork 86
NC | lifecycle | add expire delete marker rule #8961
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NC | lifecycle | add expire delete marker rule #8961
Conversation
b000007
to
ec6cc47
Compare
src/manage_nsfs/nc_lifecycle.js
Outdated
versions_list = await this.load_versions_list(object_sdk, bucket_json, rule_state); | ||
} | ||
const candidates = []; | ||
const filter_func = this._build_lifecycle_filter({filter: lifecycle_rule.filter, expiration: 0}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when having an expired delete marker we don't care if there is also expiration by days/date?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its a separate rule than both of them. also I think you can't even put expired delete marker and days/date together
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm IIRC if days is set then automatically expired delete marker = true, right?
does it mean that the expired delete marker is on objects that passed the expiration days?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
according to aws:
You can't specify both a Days and an ExpiredObjectDeleteMarker tag on the same rule. When you specify the Days tag, Amazon S3 automatically performs ExpiredObjectDeleteMarker cleanup when the delete markers are old enough to satisfy the age criteria. To clean up delete markers as soon as they become the only version, create a separate rule with only the ExpiredObjectDeleteMarker tag.
so I guess you are correct. I'll change this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and expire date + expire delete marker based on aws?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trying to put date and expire delete marker together returns MalformedXML error. there is nothing on AWS documentation about about implicit ExpiredObjectDeleteMarker when having date rule. so I guess we can't have both of them together
7f30b55
to
f0d565d
Compare
f0d565d
to
fcfff6c
Compare
fcfff6c
to
2cb1c4d
Compare
Signed-off-by: nadav mizrahi <[email protected]>
2cb1c4d
to
f216a3b
Compare
Describe the Problem
added expire delete marker rule. see https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-configuration-examples.html#lifecycle-config-conceptual-ex7
Explain the Changes
Issues: Fixed #xxx / Gap #xxx
Testing Instructions:
sudo npx jest test_nc_lifecycle_cli