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.
Configuration file
Commands read from and write to .dhcore.ini, located in the user's home directory by default. The path can be overridden by setting the DH_CONFIG environment variable.
Global flags
The following flags are available on every command:
-v, --verboseOptional. Boolean. Enable verbose output.--debugOptional. Boolean. Enable HTTP debug logging (implies verbose).
Project fallback
Commands that take -p project will fall back to the PROJECT_NAME environment variable if the flag is omitted.
register
register takes the following parameters:
-e environmentOptional. Name of the environment to register. If missing, thedhcore_namereturned by the endpoint is used.-f, --forceOptional. Boolean. Override an existing environment that points to a different endpoint.endpointMandatory. Trailing/is added automatically if missing.
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. The endpoint's .well-known/configuration and .well-known/openid-configuration are fetched and stored in a section named after the environment. This environment will be set as default, unless one is already set. If a section with the same name already exists with a different endpoint, the command will refuse to overwrite it unless --force is 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 -e example
remove
remove takes the following parameters:
environmentMandatory
dhcli remove example
init
init creates or activates a Python virtual environment and installs the platform's Python packages (digitalhub[full] and digitalhub-runtime-python). Python 3.9–3.12 must be available as python3. It takes the following parameters:
-e environmentOptional--preOptional. Boolean. Include pre-release (beta) versions when installing packages.pathOptional. Filesystem path of the virtual environment. If missing, the current environment name is used; if that is also empty, the current directory is used.
dhcli init ./venv
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 to-nfor projects.-n nameOptional (ignored) when creating resources other than projects, alternative to-ffor projects.-r, --reset-idOptional. Boolean. If set, theidspecified in the file is ignored and a new one is generated server-side.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 -r 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. Filter by kind.-s stateOptional. Filter by state.resourceMandatory
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 will return the latest version of the resource matching the name.resourceMandatoryidAlternative to-n name.
At least one of id or -n name should be provided to identify the resource. 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.-y, --confirmOptional. Boolean. If omitted, confirmation will be asked.-c, --cascadeOptional. Boolean, only applies to projects. When set, all resources belonging to the project will also be deleted.resourceMandatoryidAlternative to-n name, will delete a specific version. For projects, since versions do not apply, this is synonym withname.
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, --fn-name name_of_functionIgnored if--fn-idis specified, otherwise mandatory and will run the latest version of the function.-i, --fn-id idAlternative to--fn-name.-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 a run. The resource type is implicitly runs. 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 is derived from the run's task.-f, --followOptional. Boolean. Will keep updating the printed logs periodically (every 5 seconds) if set.idMandatory. ID of the run.
Retrieve and follow logs from the main container of a run:
dhcli log -p my-project -f 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 run. The resource type is implicitly runs. It takes the following parameters:
-e environmentOptional-p projectMandatoryidMandatory. ID of the run.
Stop a run:
dhcli stop -p my-project my-run-id
download
Downloads a resource. It takes the following parameters:
-e environmentOptional-p projectMandatory-n nameAlternative toid, will download latest version.-d, --destination output_filename_or_dirOptional, base directory or filename for downloaded resources, will be created if missing.-o output_formatOptional. Acceptsshort,json,yaml. Affects the printed metadata, not the downloaded payload.-v, --verboseOptional. Boolean. Verbose progress/logging.resourceMandatoryidAlternative to-n name.
Download an artifact:
dhcli download -p my-project -d downloaded_artifacts artifact my-artifact-id
upload
Uploads a resource to S3. The destination bucket defaults to datalake and can be overridden via the s3_bucket configuration entry. It 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.-v, --verboseOptional. Boolean. Verbose progress/logging.resourceMandatoryidMust be omitted for new artifacts; used to update an existing artifact.
Upload an artifact:
dhcli upload -p my-project -f artifacts/artifact.csv -n my-artifact artifact
services
Lists runs filtered by action=serve. It takes the following parameters:
-e environmentOptional-o output_formatOptional. Acceptsshort,json,yaml. Defaults toshort.-p projectMandatory-n nameOptional. If present, will return all versions of the specified service.-k kindOptional. Filter by kind.-s stateOptional. Filter by state. Defaults toRUNNINGwhen not specified.
List services in a project:
dhcli services -p my-project
proxy
Starts a local HTTP proxy that forwards requests to the baseUrl resolved from a run, going through the configured remote proxy with the appropriate Authorization header. It takes the following parameters:
-e environmentOptional-p projectMandatory-l, --local-port portOptional. Local port to listen on. If missing, a random port is chosen.run-idMandatory
Start a proxy for a run:
dhcli proxy -p my-project my-run-id
config
Prints the non-secret configuration of the current (or specified) environment.
-e environmentOptional-o output_formatOptional. Acceptsshort,json,yaml. Defaults toshort.
dhcli config
credentials
Prints the credentials (secret values) stored for the current (or specified) environment.
-e environmentOptional-o output_formatOptional. Acceptsshort,json,yaml. Defaults toshort.
dhcli credentials