connection discover-data-asset
Discover a data asset.
Syntax
cpd-cli connection discover-data-asset \
[--catalog-id=<catalog-id>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-config-location>] \
--data-asset-id=<data-asset-id> \
[--detail=true|false] \
[--fetch=<asset-type1,asset-type2,...>] \
[--filters=<json-filter>] \
[--jmes-query=<jmespath-query>] \
[--limit=<resource-limit>] \
[--offset=<resource-offset>] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
[--path=<asset-file-path>] \
--profile=<cpd-configuration-profile-name> \
[--project-id=<cpd-project-id>] \
[--properties=<connections-properties>] \
[--quiet] \
[--raw-output=true|false] \
[--space-id=<space-identifier>] \
[--verbose]
Arguments
The connection discover-data-asset
command has no arguments.
Options
Option | Description |
---|---|
--catalog-id |
Specify either a catalog ID,
project ID, or space ID (specify only one).
|
--context |
Specify whether assets are discovered for the purpose of reading (source) or writing (target). 'source' is the default when
no value is specified.
|
--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).
|
--data-asset-id |
Specify the data asset ID.
|
--detail |
When the option is set to 'true', additional asset-specific details are returned. When the option is set to 'false' specified, the details are
not returned.
|
--fetch |
Specify whether to return the
asset's metadata, the asset's data, interaction properties, connection properties, or the data
source type. 'metadata' is the default when the option is not specified. The option applies only
when requesting details about a data set. Use a comma-separated string to specify multiple fetch
values (for example,
--fetch=data,metadata,interaction,connection,datasource_type).
|
--filters |
Specify a custom filters *.json
file path. The default filters work for most cases.
|
|
Display command
help.
|
--jmes-query |
The Lucene
query.
|
--limit |
Specify the total number of
resources.
|
--offset |
Specify the 0-based index of the first result to return (for example, --offset=200). The default offset of 0 is used when no value is specified.
|
--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.
|
--path |
Specify the asset file path.
|
--profile |
The profile-name from the Cloud
Pak for Data configuration.
|
--project-id |
Specify a Cloud Pak for Data project instance.
|
--properties |
Specify a JSON object
that contains a set of properties to configure asset browsing
aspects.
|
--quiet |
Suppress verbose messages.
|
--raw-output |
When set to true, single values in
JSON output mode are not surrounded by quotes.
|
--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.
-
export DATA_ASSET_ID=<The data asset identifier> export OUTPUT_TYPE=<The output format ('json', 'yaml', or 'text')> export PROJECT_CPD_INSTANCE=<The Cloud Pak for Data project instance>
- Discover a data asset.
-
cpd-cli connection discover-data-asset \ --data-asset-id=${DATA_ASSET_ID} \ --output=${OUTPUT_TYPE} \ --project-id=${PROJECT_CPD_INSTANCE}