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
- Generating API Input Parameter Skeleton in JSON Format
- Checking Command
- Specifying Region
- Calling APIs with AK/SK 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
- Polling Results
- Obtaining CLI Examples on API Explorer
- Using KooCLI in Non-configuration Mode
- Online Experience
- 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
- General Reference
On this page
Show all
Help Center/
Koo Command Line Interface/
FAQs/
Profiles/
Which Profile Will Be Used by Default If No Profile Is Specified in a Command?
Copied.
Which Profile Will Be Used by Default If No Profile Is Specified in a Command?
Background
When you use KooCLI to manage and use your cloud service resources, it preferentially uses the profile specified by the --cli-profile option in the command during an API call.
If no profile is specified in the command, the default profile is used to call the target API.
If the profile does not match the target API or a parameter required for access to the target API is missing, an error message is displayed, for example:
- [USE_ERROR] Specify cli-region.
- [USE_ERROR] The value of cli-region is not supported. Supported regions: *
- [USE_ERROR] The following parameters are required: project_id
- [USE_ERROR] cli-domain-id is required for access to global services using AK/SK. Add this parameter or run `hcloud configure set` to configure it.
Solution
- If you specify a profile with --cli-profile in the command, run the hcloud configure show --cli-profile=${profileName} command to view the profile, and check whether the specified profile is proper.
- If no profile is specified in the command, the default profile is used to call the target API. Run the hcloud configure show command to query details about the default profile.
- To use other profiles, run the hcloud configure list command to view all the configured profiles, use --cli-profile=${profileName} in the API calling command to specify the name of the target profile, and try again.
Parent topic: Profiles
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot