Update to Zilliz

{
  "description": "Use when the user wants to create, list, describe, or delete an on-demand (Vector Lake / VectorLake) cluster. On-demand clusters auto-suspend after an idle TTL and are intended for ad-hoc query workloads against a Vector Lake.",
  "included_files": [],
  "name": "on-demand-cluster",
  "skill_md_contents": "---\nname: on-demand-cluster\ndescription: Use when the user wants to create, list, describe, or delete an on-demand (Vector Lake / VectorLake) cluster. On-demand clusters auto-suspend after an idle TTL and are intended for ad-hoc query workloads against a Vector Lake.\n---\n\n## Prerequisites\n\n1. CLI installed and logged in (see setup skill).\n2. A Vector Lake instance in the target project/region (see cluster\n   skill -- `cluster create-vectorlake`).\n\n## Commands Reference\n\n### Create an On-Demand Cluster\n\n`create` is hand-written and not generated from the JSON model. It calls\n`POST /v2/clusters/createOnDemandCluster` and accepts:\n\n```bash\nzilliz on-demand-cluster create \\\n  --project-id <project-id> \\\n  --region-id <region-id> \\\n  --cu-size <integer>            # required, >= 8\n  --cluster-name <string> \\      # required, max 64 chars, letters/digits/space/_/-/CJK\n  [--session-ttl <duration>] \\   # auto-suspend TTL: 30m, 1h, 90s (min 60s, default 60s)\n  [--max-query-node-cu <n>] \\\n  [--max-query-node-replicas <n>]\n```\n\nSession TTL controls how long an idle on-demand cluster stays running before\nit is automatically suspended. Format is `<number><s|m|h>`, with a floor of\n60 seconds. Resuming a suspended on-demand cluster happens transparently on\nthe next query.\n\nExamples:\n\n```bash\n# Create an 8-CU on-demand cluster with the default 60s idle TTL\nzilliz on-demand-cluster create \\\n  --project-id proj-xxxx \\\n  --region-id aws-us-east-1 \\\n  --cu-size 8 \\\n  --cluster-name \"qc-prod-1\"\n\n# Keep alive 30 minutes between queries, cap query node CU and replicas\nzilliz on-demand-cluster create \\\n  --project-id proj-xxxx \\\n  --region-id aws-us-east-1 \\\n  --cu-size 16 \\\n  --cluster-name \"qc-batch-1\" \\\n  --session-ttl 30m \\\n  --max-query-node-cu 16 \\\n  --max-query-node-replicas 4\n```\n\n### List On Demand Clusters\n\n```bash\nzilliz on-demand-cluster list --project-id <project-id> --region-id <cloud-region>\n```\n\n### Describe an On Demand Cluster\n\n```bash\nzilliz on-demand-cluster describe --cluster-id <on-demand-cluster-id>\n```\n\n### Delete an On Demand Cluster\n\n```bash\nzilliz on-demand-cluster delete --cluster-id <on-demand-cluster-id-to-delete>\n```\n\n## Guidance\n\n- On-demand clusters belong to a Vector Lake instance and only exist inside a `<projectId>` + `<regionId>` pair. If neither `list` nor `describe` returns anything, first confirm that the project has a Vector Lake (`zilliz cluster create-vectorlake`).\n- `list` requires both `--project-id` and `--region-id` -- there is no all-projects listing.\n- Status flows through `CREATING` -> `RUNNING` -> `SUSPENDING` -> `SUSPENDED` and back to `RESUMING` -> `RUNNING` on the next query. Treat `SUSPENDING`/`SUSPENDED` as healthy idle state, not an error.\n- `--session-ttl` is the idle auto-suspend timer. The minimum is `60s`; values smaller than that are rejected client-side before the API call. The current default is `60s`, so on-demand clusters are aggressive about suspending -- raise it (e.g. `30m`) when running interactive workloads.\n- `--cu-size` must be >= 8 and `--cluster-name` is at most 64 characters, allowing letters, digits, space, `_`, `-`, and Chinese characters.\n- `delete` is irreversible and asynchronous -- always confirm with the user before invoking. The cluster row moves to `DELETING` and disappears once cleanup finishes.\n- These commands are distinct from the regular `cluster` skill: a regular cluster owns its own compute, while on-demand clusters share storage with their parent Vector Lake. Do not confuse `zilliz on-demand-cluster delete` with `zilliz cluster delete`.\n"
}