asset update
Important: IBM Cloud Pak® for Data
Version 4.7 will reach end of support (EOS) on 31 July, 2025. For more information, see the Discontinuance of service announcement for IBM Cloud Pak for Data Version 4.X.
Upgrade to IBM Software Hub Version 5.1 before IBM Cloud Pak for Data Version 4.7 reaches end of support. For more information, see Upgrading IBM Software Hub in the IBM Software Hub Version 5.1 documentation.
Edit existing asset properties if you have appropriate permissions.
Syntax
cpd-cli asset update \
--asset-id=<asset-guid> \
[--catalog-id=<catalog-id>] \
[--classification=<asset-classification>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-scope>] \
[--description=<description>] \
[--jmes-query=<jmespath-query>] \
--json-patch=<json-array> \
[--name=<update-name>] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
--profile=<cpd-configuration-profile-name> \
[--project-id=<cpd-project-id>] \
[--quiet] \
[--raw-output=true|false] \
[--resource-key=<resource-key>] \
[--source-system=<source-system-information>] \
[--space-id=<space-identifier>] \
[--tags=<tag1,tag2,...>] \
[--verbose] \
[--x-open-id-connect-id-token=<x-open-id-connect-id-token>]
Arguments
The asset update 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).
|
--classification |
Specify the asset
classification.
|
--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.
|
--description |
Specify a data
asset
description.
|
|
|
Display command
help.
|
--jmes-query |
The Lucene
query.
|
--json-patch |
Specify a JSON array of patch
operations as defined in RFC 6902. For more information, see
http://jsonpatch.com.
|
--name |
Specify the updated asset
name.
|
--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 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 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.
|
--resource-key |
Specify an updated resource
key.
|
--source-system |
Specify custom data that is
associated with an object.
|
--space-id |
Specify a space
identifier.
|
--tags |
Specify the data asset tags.
Multiple tags can be specified.
|
--verbose |
Logs include more detailed
messages.
|
Table 1: Command options
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 install variables script. For more information, see Best practice: Setting up install variables.
- Specify the environment variables in a script file.
-
asset_id = <Specify the asset GUID.> project_id = <The Cloud Pak for Data project instance.> space_id = <Specify the deployment space identifier.> - Edit existing asset properties if you have appropriate permissions.
-
cpd-cli asset update \ --asset-id=${asset_id} \ --json-patch=<Specify a JSON array of patch operations as defined in RFC 6902. For more information, see http://jsonpatch.com.> \ --project-id=${PROJECT_CPD_INST_OPERANDS} \ --space-id=${space_id}