CMS CLI — aliyun cms2

Prerequisite Check

1. Check aliyun exists — which aliyun (macOS/Linux) or where aliyun (Windows).

   • Not found → ask the user to install the aliyun CLI first: \x3Chttps://help.aliyun.com/document_detail/121541.html>. Stop and wait.

2. Check CLI version — run aliyun version. Minimum required: 3.3.15 (see compatibility in frontmatter).

   ⚠️ Compare version segments as integers (semver): 3.3.4 \x3C 3.3.15 because 4 \x3C 15. Shell verification: printf '%s\ ' "3.3.15" "$(aliyun version)" | sort -V | head -1 If the output equals the current version, the requirement is NOT met.

   • Version OK → go to step 3.
   • Version too old or unrecognized →
     1. Run aliyun upgrade --help to test whether the upgrade subcommand exists.
        • Available → run aliyun upgrade -y to update to the latest version automatically, then re-check aliyun version.
     2. If upgrade not available → run curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash, then re-check aliyun version.
     3. If upgrade succeeded → go to step 3.
     4. If upgrade failed → ask the user to upgrade manually: \x3Chttps://help.aliyun.com/zh/cli/update-cli>. Stop and exit.

3. Check cms2 plugin — run aliyun cms2 --help.

   • Help output OK → continue to Credentials.
   • unknown command / missing → stop immediately, output the error report below (append CLI version, OS, and error message), and make no further CLI calls.

Credentials

aliyun cms2 reuses the aliyun CLI credential system (aliyun configure). Use --profile \x3Cname> to switch profiles.

AI-Mode

Execute the following before and after business commands:

# Before — enable AI-Mode and set User-Agent
aliyun configure ai-mode enable
aliyun configure ai-mode set-user-agent --user-agent "AlibabaCloud-Agent-Skills/alibabacloud-cms-manage"
aliyun plugin update

# ... execute business commands (aliyun cms2 ...) ...

# After — disable AI-Mode
aliyun configure ai-mode disable

Global Conventions

Hard constraint: fallback to aliyun cms, other API versions, or any workaround is strictly prohibited.

Always run aliyun cms2 \x3Ccommand> [subcommand] --help first to get the full flag list and examples.

• Prefer -o text (default) to reduce token consumption for list/get; use -o json only when indented JSON is needed.
• Before onboarding concrete resource IDs, verify them with entity query --source CloudResource; do not rely on ID shape alone.
• entity query default time range: when the user does not specify --from/--to, default to the last 7 days (--from = now − 7d, --to = now, both as Unix seconds).

Error Handling

Error codes and actions are listed in aliyun cms2 --help. Additional tips:

• InvalidJSON usually means malformed --body; validate with jq . \x3C\x3C\x3C'\x3Cvalue>' before passing to the CLI.
• --body and stdin are mutually exclusive; specify only one — means both --body (or --file) and stdin data were provided. Fix: keep only one input source. In agent/CI environments where stdin may be a pipe, append \x3C /dev/null to the command to ensure stdin is empty.

Module Routing

Commands not listed above — see aliyun cms2 --help.