-
Notifications
You must be signed in to change notification settings - Fork 184
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
[Bug] PutObjectLegalHold and PutObjectRetention changes underlying S3 file #157
Comments
I‘m very sure we haven’t implemented that, yet, and the requests are being treated as normal PUT requests... Would you be open for contributing that feature? |
See #213 Then, a new handler method could be implemented that handles the requests mentioned here. |
This is GET/PUT API-support *ONLY*. S3Mock does not enforce the legal hold. Fixes #157
This is GET/PUT API-support *ONLY*. S3Mock does not enforce the legal hold. Fixes #157
This is needed to properly support Retention and LegalHold. Fixes #157
This is needed to properly support Retention and LegalHold. Use SDKv2 in cleanup, remove legal hold before delete. Fixes #157
Half of this is implemented, Retention is next. |
S3Mock currently does not enforce retention. Fixes #157
Still not 100% sure what's going on here... Fixes #157
Use millis resolution for Instant in tests, test fails in CI. S3Mock currently does not enforce retention. Fixes #157
We have to exactly match the behaviour of the AWS SDKs here, it's easier to just depend on their internal SDK classes instead of replicating or copying the code. Not sure if I may have violated their license before by including their source code without explicitly stating that it's their copyrighted code. Fixes #157
Ran IntegrationTests against S3, fixed responses and tests accordingly. Fixes #157
We should always follow SemVer, which we did not do for previous releases. Fixes #157
Took longer than expected, but we can finally close this issue. :) Just released |
Calling PutObjectLegalHold and PutObjectRetention changes underlying S3 file for dockerized s3 mock.
Steps to reproduce:
The text was updated successfully, but these errors were encountered: