| name | hcloud-cli |
| description | Guide agents to use Huawei Cloud KooCLI correctly and safely. Use when a user asks to run or explain Huawei Cloud CLI, hcloud, hwcloud cli, KooCLI, Huawei Cloud resource inspection, IAM/profile setup, ECS/VPC/EVS/OBS/RDS/CCE or other Huawei Cloud operations from a terminal, including read-only queries, command discovery, API calls, JSON output, troubleshooting, or preparing mutating commands. |
Huawei Cloud CLI
Use Huawei Cloud KooCLI through the hcloud binary. Users may call it "hwcloud cli"; treat that as KooCLI unless the local environment proves otherwise.
Workflow
- Resolve the binary with
command -v hcloud; if absent, tell the user KooCLI is not installed and stop before inventing commands.
- Inspect local context before operating:
hcloud version
hcloud configure list
hcloud configure show
- Confirm the active profile,
--cli-region, project ID, IAM account, and endpoint context before any resource query that depends on them.
- Use
hcloud help, hcloud <service> --help, and hcloud <service> <operation> --help to discover exact names and flags. Do not assume AWS/Azure/GCP command names.
- Prefer structured output for follow-up processing: use JSON output and query/filter flags when available.
- For unsupported or unfamiliar service operations, use Huawei Cloud API Explorer or KooCLI help to map the REST API to
hcloud <service> <operation>.
- Summarize results with region/profile/project context so the user can see what account scope was queried.
Command Reference
Read references/cli-usage.md when you need exact command patterns for configuration, output formatting, OBS, dry runs, debugging, or troubleshooting.
Safety
Treat create, update, delete, stop, start, restart, reboot, resize, attach, detach, bind, unbind, grant, revoke, upload, download-to-sensitive-path, overwrite, and any operation with write/delete side effects as mutating.
Before running a mutating command, get explicit confirmation in the current conversation. Present the exact command, active profile, --cli-region, project ID, target resource identifiers, and expected effect. Use --dryrun or --debug when useful before the confirmed execution.
Never print or persist access keys, secret keys, security tokens, passwords, private keys, cookies, or decrypted configuration. If authentication is missing, guide the user to configure credentials locally; do not ask them to paste secrets into chat.
