Hi, could you update the status of the BZ please

Sam,

It looks like this was started upstream with https://github.com/ceph/ceph/pull/3409/files. What additional work do we need here?

morning, could we have an update about this RFE?

I'm not sure that that PR addresses this bz at all.  All that PR does is make it harder to accidentally delete or mess with a whole pool.  It sounds like this user wants per-rgw-object (for example) control over deletion and modification, and for that to propagate down to the rados level.  We'd need better definition on exactly what operations the user wants to disallow.  Presumably the user would want to map some rgw level authenticated users as capable of tagging and untagging the objects.  Those users would probably need to map onto rados level users and be enforced there.  It would be pretty weird to try to enforce this at the rados level since rgw object modification doesn't look like a rados level object modification at all -- it's a bucket update, an object creation, and an object removal.  By the time the "object removal" happens at the rados level, the rgw level object has already been logically updated at the rgw level, so disallowing that wouldn't even really do the trick.

No plans for this in the short term.