acl

From README

Prerequisites CLI installed and logged in (see skill). No cluster context required -- these are control-plane operations. The /v2/roles, /v2/members, and /v2/groups routes must be enabled for the caller's endpoint. They are still rolling out: a 404 from any zilliz acl command means the API is not live there yet. Commands Reference zilliz acl is a three-level tree -- acl role, acl member, and acl group. It is deliberately absent from zilliz --help and shell completion while the routes roll out, but every command below runs today and every --help under it works. Roles --project-id on describe, principals, and delete is the project boundary of a pre-defined project role, which carries none of its own. A custom role is addressed by ID alone. Create and update a role Only project roles can be created; the API has no org-role create path. update replaces the policy wholesale -- it never merges -- and prompts before shrinking the statement count unless -y is passed.