priyeshkaratha opened a new pull request, #11817:
URL: https://github.com/apache/ozone/pull/11817
## What changes were proposed in this pull request?
`OMLifecycleConfigurationSetRequest` does its validation in `preExecute`: it
resolves the bucket link,
checks ACLs, verifies the requested bucket layout matches the bucket, and
validates
AbortIncompleteMultipartUpload days. `validateAndUpdateCache` then looks the
bucket up again by name under
the bucket lock and stores the configuration with that bucket's object ID.
If the bucket is deleted and recreated with the same name between
`preExecute` and the Ratis apply, the
configuration is attached to the new bucket, even though it was validated
against the old one (whose
ACLs, owner or layout may differ).
This PR binds the request to the bucket it was validated against:
- `preExecute` reads the bucket and sets
`LifecycleConfiguration.bucketObjectID` in the request. Any
client-supplied value is overwritten.
- `validateAndUpdateCache` rejects the request with `BUCKET_NOT_FOUND` if
the field is set and does not
match the current bucket's object ID.
## What is the link to the Apache JIRA
HDDS-17245
## How was this patch tested?
Updated testcases
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
