asset attribute get
Retrieve an asset attribute.
Syntax
cpd-cli asset attribute get \
--asset-id=<asset-guid> \
--attribute-key=<attribute-key> \
--profile=<cpd-profile-name> \
[--catalog-id=<catalog-id>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-scope>] \
[--jmes-query=<jmespath-query>] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
[--project-id=<project-id>] \
[--quiet] \
[--revision-id=<revision-id>] \
[--raw-output=true|false] \
[--space-id=<space-identifier>] \
[--verbose]
Arguments
The asset attribute get command has
no arguments.
Options
Table 1: Command options
| Option | Description |
|---|---|
--asset-id |
Specify the asset
GUID.
|
--attribute-key |
Specify the attribute
key.
|
--catalog-id |
Specify either a catalog ID,
project ID, or space ID (specify one only).
|
--context |
Specify the configuration context
name.
|
--cpd-config |
The IBM Software Hub
configuration location. For example,
$HOME/.cpd-cli/config.
|
--cpd-scope |
The IBM Software Hub space,
project, or catalog scope. For example,
cpd://default-context/spaces/7bccdda4-9752-4f37-868e-891de6c48135.
|
|
|
Display command
help.
|
--jmes-query |
Provide a JMESPath query to
customize the output.
|
--output |
Specify an output
format.
|
--output-file |
Specify a file path where all
output is redirected.
|
--profile |
The name of the profile that you
created to store information about an instance of Cloud Pak for Data and your credentials for the
instance.
|
--project-id |
Specify an IBM Software Hub
project instance.
|
--quiet |
Suppress verbose
messages.
|
--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.
|
--raw-output |
When set to true, single values
are not surrounded by quotation marks in
JSON output
mode.
|
--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 add the listed
environment variables to the installation variables script. For more information, see Setting up installation environment variables.
- Specify the environment variables in a script file.
-
asset_id = <The asset GUID> space_id = <The deployment space identifier> - Retrieve an asset attribute.
-
cpd-cli asset attribute get \ --asset-id=${asset_id} \ --attribute-key=<Specify an attribute key> --project-id=zen \ --space-id=${space_id}