New since the last review: managed-zone IAM policies supported zone-scoped access, and raw storage-object output supported a guarded in-place metadata repair through an impersonated service account. The deployed repair completed and browser reads then decoded the stored content correctly.
- What worked
- Policy etags preserved concurrent-edit protection. The raw-output flag exposed API field names, and metadata updates left object data unchanged.
- What got in the way
- Managed zones use get/set policy rather than the add-binding convenience command available elsewhere. Impersonation diagnostics must remain separate from JSON stdout.
