feat: add unset command to remove object-lock configuration from buckets #1339
+125
−2
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.
What does this PR do?
Implements the 'unset' command for removing object-lock configurations on buckets.
The command sends a PUT request with a customizable XML body to the specified bucket
URL, allowing different combinations of object-lock settings, such as disabling
lock retention or clearing rules.
Changes include:
Addition of the unset command logic and related parameter handling.
Dynamic XML body generation to accommodate different server requirements.
Logging adjustments to display the actual request body sent to the server.
How Has This Been Tested?
Unit Tests: Describe the unit tests you have written and their outcomes.
Integration Tests: Detail the integration tests performed and their results.
Manual Testing: Explain the manual testing process, including steps taken and evidence such as screenshots or logs.
Checklist
pre-commit run --all-files
Screenshots/Videos