CLI commands
Available CLI commands and their parameters are listed here. In these examples, the executable is named dhcli.
If you need to install the CLI, refer to this section.
Run commands
Depending on the shell you are using, you may have to run the CLI with ./dhcli.
register
register takes the following parameters:
-e environmentOptional. Name of the environment to register.core_endpointMandatory
dhcli register -e example http://localhost:8080
.dhcore.ini file (if it doesn't already exist) in the user's home directory, or, if not possible, in the current one. A section will be appended, using the provided environment name (or, if missing, the one returned by the endpoint), containing the environment's configuration. This environment will be set as default, unless one is already set.
list-env
list-env lists available environments. It takes no parameters.
dhcli list-env
use
use takes the following parameters:
environmentMandatory
dhcli use example
login
login is to be used after registering an environment with the register command. It takes the following parameters:
-e environmentOptional.
dhcli login -e example
refresh
refresh is to be used after the login command, to update access_token and refresh_token. It takes the following parameters:
-e environmentOptional
dhcli refresh example
remove
remove takes the following parameters:
environmentMandatory
dhcli remove example
init
init is used to install the platform's Python packages; therefore, Python must be installed. It takes the following parameters:
-e environmentOptional
dhcli init example
create
create will create an instance of the indicated resource on the platform. It takes the following parameters:
-e environmentOptional-p projectOptional (ignored) when creating projects, mandatory otherwise.-f yaml_file_pathMandatory when creating resources other than projects, alternative tonamefor projects.-n nameOptional (ignored) when creating resources other than projects, alternative toyaml_file_pathfor projects.-reset-idOptional. Boolean. If set, theidspecified in the file is ignored.resourceMandatory
The type of resource to create is mandatory. The project flag -p is only mandatory when creating resources other than projects (artifacts, models, etc.). For projects, you may omit the file path and just use the -n flag to specify the name. The -reset-id flag, when set, ensures the created object has a randomly-generated ID, ignoring the id field if present in the input file (this is not relevant to projects).
Create a project:
dhcli create -f samples/project.yaml projects
Create an artifact, while resetting its ID:
dhcli create -p my-project -f samples/artifact.yaml -reset-id artifacts
list
list returns a list of resources of the specified type. It takes the following parameters:
-e environmentOptional-o output_formatOptional. Acceptsshort,json,yaml. Defaults toshort.-p projectOptional (ignored) for projects, mandatory otherwise.-n nameOptional. If present, will return all versions of specified resource. If missing, will return the latest version of all matching resources.-k kindOptional-s stateOptionalresourceMandatory
output_format determines how the output will be formatted. The default value, short, is meant to be used to quickly check resources in the terminal, while json and yaml will format the output accordingly, making it ideal to write to file.
List all projects:
dhcli list projects
List all artifacts in a project:
dhcli list -p my-project artifacts
Note that you can easily write the results to file by redirecting standard output:
dhcli list -o yaml -p my-project artifacts > output.yaml
get
get returns the details of a single resource. It takes the following parameters:
-e environmentOptional-o output_formatOptional. Acceptsshort,json,yaml. Defaults toshort.-p projectOptional (ignored) for projects, mandatory otherwise.-n nameIgnored ifidis present, otherwise mandatory and will return the latest version of the specified resource.resourceMandatoryidAlternative to-n name.
Similarly to the list command, output_format determines how the output will be formatted. The default value, short, is meant to be used to quickly check resources in the terminal, while json and yaml will format the output accordingly, making it ideal to write to file.
Get project:
dhcli get projects my-project
Get artifact:
dhcli get -p my-project artifacts my-artifact-id
Get artifact and write to file:
dhcli get -o yaml -p my-project artifacts my-artifact-id > output.yaml
update
update will update a resource with a new definition. It takes the following parameters:
-e environmentOptional-p projectOptional (ignored) for projects, mandatory otherwise.-f yaml_file_pathMandatoryresourceMandatoryidMandatory
Update a project:
dhcli update -f samples/project.yaml projects my-project
Update an artifact:
dhcli update -p my-project -f samples/artifact.yaml artifacts my-artifact-id
delete
delete will delete a resource. It takes the following parameters:
-e environmentOptional-p projectOptional (ignored) for projects, mandatory otherwise.-n nameAlternative toid, will delete all versions of a resource.-yOptional. Boolean. If omitted, confirmation will be asked.-cOptional. Boolean, only applies to projects. When set, all resource belonging to the project will also be deleted.resourceMandatoryidAlternative toname, will delete a specific version. For projects, since versions do not apply, this is synonym withid.
Delete a project and all of its resources:
dhcli delete -c projects my-project
Delete an artifact, skip confirmation:
dhcli delete -p my-project -y artifacts my-artifact-id
run
Creates a run of the specified function. It takes the following parameters:
-e environmentOptional-p projectMandatory-n name_of_functionIgnored ifidis specified, otherwise mandatory and will run the latest version of the function.-i idAlternative to-n name_of_function.-f yaml_file_pathOptional, can contain additional parameters for the run.taskMandatory. Must contain a valid task, such aspython+build.
Create a python+build run of latest version of my-function:
dhcli run -p my-project -n my-function python+build
log
Returns the logs of the specified resource. It takes the following parameters:
-e environmentOptional-p projectMandatory-c containerOptional, ID of the container to read logs from. If not specified, the main container will be picked.-fOptional, will update the printed logs periodically if set.resourceMandatoryidMandatory
Retrieve and follow logs from the main container of a run:
dhcli log -p my-project run my-run-id
metrics
Returns metrics for the specified resource. It takes the following parameters:
-e environmentOptional-p projectMandatory-c containerOptional, ID of the container to read metrics from. If not specified, the main container will be picked.resourceMandatoryidMandatory
Retrieve metrics from the main container of a run:
dhcli metrics -p my-project run my-run-id
stop
Stops a resource. It takes the following parameters:
-e environmentOptional-p projectMandatoryresourceMandatoryidMandatory
Stop a run:
dhcli stop -p my-project run my-run-id
resume
Resumes a resource. It takes the following parameters:
-e environmentOptional-p projectMandatoryresourceMandatoryidMandatory
Resume a run:
dhcli resume -p my-project run my-run-id
download
Downloads a resource. It takes the following parameters:
-e environmentOptional-p projectMandatory-n nameAlternative toid, will download latest version.-o output_filename_or_dirOptional, base directory for downloaded resources, will be created if missing.resourceMandatoryidAlternative to-n name.
Download an artifact:
dhcli download -p my-project -o downloaded_artifacts artifact my-artifact-id
upload
Uploads a resource. takes the following parameters:
-e environmentOptional-p projectMandatory-n nameMust be specified when creating a new artifact.-f input_filename_or_dirMandatory, path to input file or directory.resourceMandatoryidMust be omitted for new artifacts; used to update an existing artifact.
Upload an artifact:
dhcli upload -p my-project -f artifacts/artifact.csv artifact -n my-artifact