Prerequisites
- Have a Heex CLI
- Have a API_KEY. Should be accessible in your personnal space on the heex cloud platform.
Usage
| Subcommand | Description |
|---|---|
| create | Create a new implementation on the cloud. |
| create-template-file | Advanced usage: creates a template file for implementation creation configuration. |
How to create a new implementation
2 different ways to create a new implementation on the cloud, both using the commandcreate:
- Create an implementation only by name and some optional description, using the 2 subcommands:
--name: Must be unique on your cloud workspace.--description: Description for your implementation.
- Another way to create an implementation is to use a configuration file that contains all the data you want to generate, if you want to use it:
- You can generate a template file using the
./heex implementation create-template-filecommand, and then fill the given file as you need. - Once it is filled, use the create subcommand with the
--input-fileinput pointing to the filled file.
- You can generate a template file using the
⚠️ 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”.
How to update an existing implementation
You can update an existing implementation using theupdate 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:
How to get implementation details
You can get the details of a implementation if you provide animplementation-id, see example below:
Usage:
How to get implementation list
You can get list of all available implementations in a given workspace. Several filters are available to narrow down the results. The flags available to filter the results are:--implementation-idID of the involved implementation. Multiple can be given: e.g.--implementation-id ID1--implementation-id ID2.--signal-idSignal IDs to retrieve details for. Multiple can be given:signal-id ID1signal-id ID1.--priorityPriority of the implementation to retrieve details for. Check the help for available values.--typeType of the implementation to retrieve details for. Check help for available values.--nameName of the implementation to retrieve details for.--output-fileThe 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: