NSFS | S3 | Lifecycle: Expiration Date in the past gets accepted

[nhaustein]

Environment info

• NooBaa Version: noobaa-core-5.17.1-20241104.el9.x86_64
• Platform: RHEL 9.2 x86

Actual behavior

1. The expiration date in the past is getting accepted, example of the lifecycle rule which gets accepted:

{
"Rules": [
{
"ID": "Expiration-date",
"Status": "Enabled",
"Filter": {
"Prefix": "small"
},
"Expiration": { "Date": "2024-01-01T00:00:00.000Z" }
}
]
}

Expected behavior

1. If expiration date is in the past relative to current date the lifecycle rule should get rejected.

Steps to reproduce

1. Please use the lifecycle rule above to recreate it.

More information - Screenshots / Logs / Other output

[achouhan09]

Hi @nhaustein
I am able to put the past/current date as expiration using aws cli, check below:

Why do you think its a bug can you explain more about it. Thanks

[nhaustein]

Hi @achouhan09, I thought it is a bug because the test suite we are using (COS) complained about this. I checked the AWS documentation and found that it is ok to provided a date in the past (https://docs.aws.amazon.com/AmazonS3/latest/userguide/intro-lifecycle-rules.html). With this finding, the issue can be closed.
Thanks and happy new year.

[achouhan09]

Closing with the comment. Thanks

Happy new year