Connect CLI usage
It is assumed that you will already have access to the Krucial CONNECT application server to create appropriate credentials for the connect CLI.
Configuration
It is necessary to configure the CLI with appropriate credentials. Your client-id and client-secret values are available via the Krucial Connect application.
Use the command below to set your configuration values:
connect-cli conf --clientId <client-id> --clientSecret <client-secret>
To verify they have been set correctly. Use the show flag:
connect-cli conf --show
To obtain further help for the conf command use the --help flag:
connect-cli conf --help
Authenticate your session
To be able to use the CLI, you must first generate a valid JWT token. This is done using the validate-krucial-client command:
connect-cli validate-krucial-client
Running Commands
For full list of commands type:
connect-cli
The structure of the project is split into "topics". The topics used in the project are defined as following:
- api-integration
- connect-plugin
- deployment
- device
- device-profile
- k-cell
- plugins
- webhook
These topics are based on the Sigma API endpoint structure and are designed to operate in the same manner. Various commands are run with these topics. To obtain a list of all commands for a particular topic, run the following:
connect-cli <topic-name> --help
connect-cli <topic-name> <command-name> --help
Known Issues
500 Internal Server Error
Most commonly occurs when your authentication token has expired. Ensure that you have run the configuration step above and then run the following command:
connect-cli validate-krucial-client