Subcommand | Description |
---|---|
get | Retrieve implementation details with a given ID. |
list | Retrieve implementations based on optional filters. |
create | Create a new implementation on the cloud. |
create-template-file | Advanced usage: creates a template file for implementation creation configuration. |
update | Update existing implementation for a given id. |
delete | Delete an implementaion with a given ID. |
create
:
--name
: Must be unique on your cloud workspace.--description
: Description for your implementation../heex implementation create-template-file
command, and then fill the given file as you need.--input-file
input pointing to the filled file.⚠️ Warning: implementation name or description with special characters If your implementation name or description contains special characters (i.e ’ or space), please use double quotes before and after your names.For example, for a implementation called Jane’s implementation, provide that as —name “Jane’s implementation”.
update
subcommand. This will command allows to add new signals to the existing implementation.
Flags implementation-id
and signal-id
are mandatory. You can provide more than one signal to add to the implementation, check help for more information.
Usage:
implementation-id
, see example below:
Usage:
--implementation-id
ID of the involved implementation. Multiple can be given: e.g. --implementation-id ID1
--implementation-id ID2
.--signal-id
Signal IDs to retrieve details for. Multiple can be given: signal-id ID1
signal-id ID1
.--priority
Priority of the implementation to retrieve details for. Check the help for available values.--type
Type of the implementation to retrieve details for. Check help for available values.--name
Name of the implementation to retrieve details for.--output-file
The result will be saved into this provided filepath. The output format is json, so please provide a filepath with that format:/path/to/file.json--output-file
flag. If the provided path doesn’t exist, it will be created. See example below where several filters can be used at the same time:
Usage:
implementation-id
. If the implementation is linked to any system, it is not possible to delete: you need to unlink it from the system(s) first and then try again.
Usage: