jojochuang commented on PR #11053: URL: https://github.com/apache/ozone/pull/11053#issuecomment-5786434078
### Observability / displaying WORM state The OEP covers **querying** lock configuration through the standard S3 Object Lock **Get** APIs (`GetBucketObjectLockConfiguration`, `GetObjectRetention`, `GetObjectLegalHold`) and Phase 3 OM / metadata-reader paths. That matches how AWS expects clients to read **bucket default config** and **per-object retention / legal hold** when they call those sub-resources explicitly (AWS CLI, Boto3, etc.). For **seeing lock state on normal object reads**, AWS documents **`HeadObject`** and **`GetObject`** response headers (when the caller has **`s3:GetObjectRetention`** / **`s3:GetObjectLegalHold`**): - `x-amz-object-lock-mode` - `x-amz-object-lock-retain-until-date` - `x-amz-object-lock-legal-hold` - (and event-hold related headers where variable retention applies) The OEP does **not** yet call out enriching **Head/Get** with those headers. That is the main **S3 parity** gap for “display WORM state without extra GET `?retention` / `?legal-hold` round trips.” **Operator tooling:** The doc does not discuss **`ozone sh` / admin / Recon** (or similar) showing `objectLockEnabled`, default retention, or effective protection on a key. The Java **`ObjectStore`** snippet shows setters only; read paths outside the six S3 Get handlers are not spelled out. Suggest a short **“Observability”** subsection: - **v1 minimum (AWS-aligned):** the three Get APIs + document **HeadObject/GetObject** lock headers and required Ranger **`Get*`** actions. - **Follow-ups (product):** CLI/Recon and read APIs on `ObjectStore` if non-S3 clients need lock metadata. -- 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]
