zilliz-cli

Zilliz CLI v1.5.0 adds access-control workflows—check the cloud and database boundary Access-control automation gets confusing when a cloud project role and a database role are treated as the same thing. For Milvus users operating on Zilliz Cloud, that distinction is worth checking before handing an admin workflow to a script or coding agent. We're sharing the CLI v1.5.0 access-control update with the community. It adds an ACL command tree for roles, members, groups, and policy grants, plus a generated skill that describes the same workflow. Policies can be supplied inline, loaded from a JSON file, or built interactively. Each path validates against an embedded action catalog before sending the request. That gives developers an earlier check on the policy they are asking the service to accept; it should not be read as a promise that a request will pass backend authorization. There are important scope and availability details in the release notes: - Project roles belong to one project. Non-interactive automation needs the relevant project context instead of relying on a terminal prompt. - Organization roles are read-only in this command set because the backend does not define create, modify, or delete actions for them. - The ACL commands remain hidden from help and shell completion until the corresponding /v2 routes are published on the API gateway. The generated zilliz:acl skill uses the same action catalog as local validation. It also distinguishes cloud organization/project access control from database RBAC. An agent choosing a command still needs to know which layer it is supposed to administer. Before adapting an existing workflow, identify the target resource, the role's scope, and the account that will execute it. Then check the release's availability notes against your environment. The release notes include supported platforms and installation options: github.com/zilliztech/zilliz-cli/releases/tag/zil…

Zilliz CLI v1.5.0 adds access-control workflows—check the cloud and database boundary Access-control automation gets confusing when a cloud project role and a database role are treated as the same thing. For Milvus users operating on Zilliz Cloud, that distinction is worth checking before handing an admin workflow to a script or coding agent. We're sharing the CLI v1.5.0 access-control update with the community. It adds an ACL command tree for roles, members, groups, and policy grants, plus a generated skill that describes the same workflow. Policies can be supplied inline, loaded from a JSON file, or built interactively. Each path validates against an embedded action catalog before sending the request. That gives developers an earlier check on the policy they are asking the service to accept; it should not be read as a promise that a request will pass backend authorization. There are important scope and availability details in the release notes: - Project roles belong to one project. Non-interactive automation needs the relevant project context instead of relying on a terminal prompt. - Organization roles are read-only in this command set because the backend does not define create, modify, or delete actions for them. - The ACL commands remain hidden from help and shell completion until the corresponding /v2 routes are published on the API gateway. The generated zilliz:acl skill uses the same action catalog as local validation. It also distinguishes cloud organization/project access control from database RBAC. An agent choosing a command still needs to know which layer it is supposed to administer. Before adapting an existing workflow, identify the target resource, the role's scope, and the account that will execute it. Then check the release's availability notes against your environment. The release notes include supported platforms and installation options: github.com/zilliztech/zilliz-cli/releases/tag/zil…

Zilliz CLI v1.5.0 adds access-control workflows—check the cloud and database boundary Access-control automation gets confusing when a cloud project role and a database role are treated as the same thing. For Milvus users operating on Zilliz Cloud, that distinction is worth checking before handing an admin workflow to a script or coding agent. We're sharing the CLI v1.5.0 access-control update with the community. It adds an ACL command tree for roles, members, groups, and policy grants, plus a generated skill that describes the same workflow. Policies can be supplied inline, loaded from a JSON file, or built interactively. Each path validates against an embedded action catalog before sending the request. That gives developers an earlier check on the policy they are asking the service to accept; it should not be read as a promise that a request will pass backend authorization. There are important scope and availability details in the release notes: - Project roles belong to one project. Non-interactive automation needs the relevant project context instead of relying on a terminal prompt. - Organization roles are read-only in this command set because the backend does not define create, modify, or delete actions for them. - The ACL commands remain hidden from help and shell completion until the corresponding /v2 routes are published on the API gateway. The generated zilliz:acl skill uses the same action catalog as local validation. It also distinguishes cloud organization/project access control from database RBAC. An agent choosing a command still needs to know which layer it is supposed to administer. Before adapting an existing workflow, identify the target resource, the role's scope, and the account that will execute it. Then check the release's availability notes against your environment. The release notes include supported platforms and installation options: github.com/zilliztech/zilliz-cli/releases/tag/zil…