Error Message
Config Subcommand Is Empty.
Symptom
The subcommand of ohpm config is empty.
Possible Causes
No subcommand is specified when the ohpm config command is executed.
Solution
Check the available subcommands for ohpm config and specify one before running the command.
Error Message
Config Subcommand Not Support.
Symptom
The subcommand for ohpm config is not supported.
Possible Causes
The subcommand specified for ohpm config is not supported.
Solution
Verify the specified subcommand for ohpm config and use a supported one.
Error Message
Config Set Command Param Error.
Symptom
Parameters for the ohpm config set command are incorrect.
Possible Causes
The <key> and <value> parameters are not configured when the ohpm config set command is executed.
Solution
Ensure that the command follows the format ohpm config set <key> <value>.
Error Message
Config Get Command Param Error.
Symptom
Parameters for the ohpm config get command are incorrect.
Possible Causes
When running the ohpm config get <key> command, multiple keys are configured at the same time, for example, ohpm config get registry log_level --log_level info.
Solution
Ensure that only one key is configured in the command. The command format must be ohpm config get <key>, for example, ohpm config get registry.
Error Message
Config Delete Command Param Error.
Symptom
Parameters for the ohpm config delete command are incorrect.
Possible Causes
The ohpm config delete command is executed without <key> specified.
Solution
Ensure that the command follows the format ohpm config delete <key>.
Error Message
Config List Command Param Error.
Symptom
Parameters for the ohpm config list command are invalid.
Possible Causes
The parameter configured for ohpm config list is invalid, for example, ohpm config list adsy.
Solution
Ensure that the command follows the format ohpm config list [-j|--json].
Error Message
Protected Key.
Symptom
Access to a protected key is denied.
Possible Causes
You attempt to run the ohpm config get _auth command to obtain a key whose name starts with an underscore (_).
Solution
Keys starting with an underscore (for example, _auth=readWriteToken) are protected and cannot be accessed. For details, see AccessToken Configuration.
Error Message
Key Not Exist.
Symptom
The key does not exist.
Possible Causes
You attempt to run the ohpm config delete <key> command to delete a key that does not exist in the user-level .ohpmrc file.
Solution
Run ohpm config list to view all available keys, identify the exact key you want to delete, and then execute ohpm config delete <key>.
Error Message
Repeat Load Configuration.
Symptom
The configuration is loaded repeatedly.
Possible Causes
The ohpm command loads parameters and configuration files multiple times during execution.
Solution
Terminate the current ohpm command process and reload the configuration.
Error Message
Not Loaded When Saving.
Symptom
The configuration file is not loaded before saving.
Possible Causes
The configuration file is not loaded before saving.
Solution
Load the configuration file before saving.
Error Message
Not Loaded When Setting.
Symptom
The configuration data is not loaded before parameter setting.
Possible Causes
The configuration data is not loaded before parameter setting.
Solution
Load the configuration data before setting parameters.
Error Message
Config Encrypt Command Param Error.
Symptom
Parameters for the ohpm config encrypt command are incorrect.
Possible Causes
The ohpm config encrypt <string> command is executed without the --crypto_path parameter specified.
Solution
Ensure that the command follows the format ohpm config encrypt --crypto_path <string>.
Error Message
Crypto Path Is Empty.
Symptom
The crypto component path is empty.
Possible Causes
The ohpm config encrypt command is executed with crypto_path not configured in the .ohpmrc file.
Solution
Error Message
Crypto Component Not Directory.
Symptom
The crypto component path is incorrect.
Possible Causes
string in ohpm config encrypt --crypto_path <string> is set to a valid existing file path rather than a folder path.
Solution
Check and ensure that the current crypto path is a folder path.
Error Message
Invalid Crypto Component.
Symptom
The crypto component is invalid.
Possible Causes
The crypto component folder is not empty, but the crypto component files inside are corrupted, or irrelevant files that do not belong to the crypto component exist in the folder.
Solution
Run the ohpm config encrypt --crypto_path <string> command to generate a valid crypto component directory. Ensure that <string> meet the requirements of the crypto component. For details, see crypto_path.
Error Message
Crypto Path Not Configured.
Symptom
The crypto path is not configured.
Possible Causes
A sensitive configuration item (for example, http_proxy=http://security:01:XXXXXX@proxy:port) is configured in the .ohpmrc file while no crypto_path for the crypto component is configured.
Solution
Correctly configure crypto_path in the .ohpmrc file. For details, see crypto_path.