asset get
Retrieve a catalog or project asset.
Syntax
cpd-cli asset get \
--asset-id=<asset-guid>
[--catalog-id=<catalog-id>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-config-location>] \
[--jmes-query=<jmespath-query>] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
--profile=<cpd-configuration-profile-name> \
[--project-id=<cpd-project-id>] \
[--quiet] \
[--raw-output=true|false] \
[--revision-id=<revision-id>] \
[--space-id=<space-identifier>] \
[--verbose]
Arguments
The asset get
command has no
arguments.
Options
Option | Description |
---|---|
--asset-id |
Specify the asset GUID.
|
--catalog-id |
Specify either a catalog ID,
project ID, or space ID (specify only one).
|
--context |
Specify the configuration context
name.
|
--cpd-config |
The Cloud Pak for Data
configuration location (for example, $HOME/.cpd-cli/config).
|
--cpd-scope |
The Cloud Pak for Data space, project, or catalog scope (for example, cpd://default-context/spaces/7bccdda4-9752-4f37-868e-891de6c48135).
|
|
Display command
help.
|
--jmes-query |
The Lucene
query.
|
--output |
Specify an output format.
Valid formats include json, yaml, or text (the default
format).
|
--output-file |
Specify a file path where all output is redirected.
|
--profile |
The profile-name from the Cloud
Pak for Data configuration.
|
--project-id |
Specify a Cloud Pak for Data project instance.
|
--quiet |
Suppress verbose messages.
|
--raw-output |
When set to true, single values in
JSON output mode are not surrounded by quotes.
|
--revision-id |
Specify a revision ID (for
example, 1, 2, 3, ...). The current asset version is used when no value is specified. Specify
'latest' for the most recent revision.
|
--space-id |
Specify a space identifier.
|
--verbose |
Logs include more detailed
messages.
|
Examples
Note: The following examples use environment variables. Use a script to create
environment variables with the correct values for your environment. You can optionally add the
listed environment variables to the install variables script. For more information, see Best practice: Setting up install variables.
- Define the environment variables.
- Replace the following properties with your
data.
export JMES_QUERY='attachments[0].object_key' export ASSET_ID=<The import identifier> export SPACE_ID=<The deployment space identifier>
- Retrieve a script from a specific space.
-
cpd-cli asset get \ --asset-id=${ASSET_ID} \ --jmes-query=${JMES_QUERY} \ --output=json \ --space-id=${SPACE_ID}