Esta página aún no está disponible en su idioma local. Estamos trabajando arduamente para agregar más versiones de idiomas. Gracias por tu apoyo.
Koo Command Line Interface
Koo Command Line Interface
- Function Overview
- What's New
- Service Overview
- Getting Started
-
User Guide
- Configuration Management
- HTTP Proxy
- Commonly Used Commands
-
Options
- Option Overview
- Printing Help Information
- Printing Debugging Information
- Checking Command
- Specifying Region
- Calling APIs with an Account in Non-configuration Mode
- Calling APIs with AK/SK in Non-configuration Mode
- Calling APIs with a Token in Non-configuration Mode
- Calling APIs Using an Agency in Non-configuration Mode
- Specifying Account ID
- Specifying Profile
- Specifying Authentication Mode
- Specifying Output Format
- Passing API Parameters with JSON File
- Specifying Request Timeouts
- Specifying Retry Count
- Skipping HTTPS Request Certificate Verification
- Specifying a Domain Name
- Obtaining CLI Examples on API Explorer
- Using KooCLI in Non-configuration Mode
- Obtaining Authentication Information
-
FAQs
- Overview
- Authentication
- Profiles
- Metadata Cache
- Logs
- Network Connections
- Cloud Services
- Cloud Service APIs
- Regions
-
Parameters
- What Are KooCLI System Parameters?
- Why Am I Seeing a Message Indicating an Invalid Parameter?
- Why Are Old and New KooCLI System Parameters (Such as region and cli-region) Available? Which Parameters Are Recommended?
- Why Am I Seeing a Message Indicating a Duplicate Parameter?
- How Do I Use cli-jsonInput?
- When Can I Use cli-jsonInput?
- Why Am I Seeing a Message Indicating an Unsupported Parameter Position or Type?
- How Do I Leave a Body Parameter Empty for Cloud Service APIs?
- Interactive Mode and Autocomplete
-
Output Formats
- What Output Formats Are Supported by KooCLI?
- How Do I Define a JMESPath Expression?
- Which KooCLI System Parameters Are Related to Data Output? Which Ones Are Recommended?
- How Do I Use cli-output, cli-query, and cli-output-num?
- How Do I Use cli-output-rows, cli-output-cols, and cli-output-num? What Are the Precautions?
- How Do I Use cli-json-filter? What Are the Precautions?
- Other
- Videos
On this page
Show all
Help Center/
Koo Command Line Interface/
Getting Started/
Step 2: Install the CLI/
Installing KooCLI in Windows
Installing KooCLI in Windows
Updated on 2023-02-27 GMT+08:00
- Download KooCLI for Windows.
- Decompress the package to obtain the hcloud.exe file, as shown in Figure 1.
- (Optional) Add the directory where KooCLI is located to the system environment variable Path so that you can run hcloud commands in any directory of Command Prompt.
- If you use Windows 10 or Windows 8, search for and select View advanced system settings, and click Environment Variables.
If you use Windows 7, right-click the Computer icon on the desktop, and choose Properties from the shortcut menu. Click the Advanced system settings link, and click Environment Variables.
- On the Environment Variables page, select Path in the user variable list, and click Edit.
- On the Edit environment variable page, click New and enter the path of the hcloud.exe file.
- Click OK on the three pages successively to save the change.
- (Optional) Open the Command Prompt, and run the following command to check whether the environment variable contains the directory where the hcloud.exe file is located. If yes, the configuration is successful.
set path
- If you use Windows 10 or Windows 8, search for and select View advanced system settings, and click Environment Variables.
- (Optional) If Step 3 is not performed, go to the directory where KooCLI is located, open the Command Prompt of Windows, and run the following command to check whether the CLI is installed successfully:
hcloud version
If version information similar to the following is displayed, the installation is successful:
hcloud version Current KooCLI version: 3.2.8
Parent topic: Step 2: Install the CLI
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.