asset data-asset create

Create an asset in the catalog or project.

Syntax

cpd-cli asset data-asset create \
--entity=<entity-map> \
--metadata=<assetmetadata-object> \
--profile=<profile-name> \
[--attachments=<asset-attachment-object>] \
[--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] \
[--raw-output=true|false] \
[--space-id=<space-identifier>] \
[--verbose]

Arguments

The asset data-asset create command has no arguments.

Options

Table 1: Command options
Option Description
--attachments The AssetAttachment object.
Status
Optional.
Syntax
--attachments=<asset-attachment-object>
Default value
No default.
Valid values
Any valid AssetAttachment object.
--catalog-id Specify either a catalog ID,
 project ID, or space ID (specify one only).
Status
Optional.
Syntax
--catalog-id=<catalog-id>
Default value
No default.
Valid values
A valid catalog, project, or space ID.
--context Specify the configuration context
 name.
Status
Optional.
Syntax
--context=<catalog-project-or-space-id>
Default value
Not applicable.
Valid values
A valid configuration context name.
--cpd-config The IBM Software Hub
 configuration location. For example, $HOME/.cpd-cli/config.
Status
Optional.
Syntax
--cpd-config=<cpd-config-location>
Default value
$HOME/.cpd-cli/config
Valid values
A valid IBM® Software Hub configuration location.
--cpd-scope The IBM Software Hub space, project, or catalog scope. For example, cpd://default-context/spaces/7bccdda4-9752-4f37-868e-891de6c48135.
Status
Optional.
Syntax
--cpd-scope=<cpd-scope>
Default value
No default.
Valid values
A valid IBM Software Hub space, project, or catalog scope.
--entity The underlying table definition.
Status
Required.
Syntax
--entity=<entity-map>
Default value
No default.
Valid values
A valid table definition map.

--help

-h

 Display command help.
Status
Optional.
Syntax
--help
Default value
No default.
Valid values
Not applicable.
--jmes-query Provide a JMESPath query to customize the output.
Status
Optional.
Syntax
--jmes-query=<jmespath-query>
Default value
No default.
Valid values
A valid JMESPath query.
--metadata The system metadata (AssetMetadata
object) regarding the table definition.
Status
Required.
Syntax
--metadata=<assetmetadata-object>
Default value
No default.
Valid values
--output Specify an output format.
Status
Optional.
Syntax
--output=json|yaml|text
Default value
text
Valid values
Valid formats include JSON, YAML, or text (the default format).
--output-file Specify a file path where all output is redirected.
Status
Optional.
Syntax
--output-file=<output-file-location>
Default value
No default.
Valid values
A valid output file path location.
--profile The name of the profile that you created to store information about an instance of IBM Software Hub and your credentials for the instance.
Status
Required.
Syntax
--profile=<profile-name>
Default value
No default.
Valid values

The name of the profile that you created.
--project-id Specify an IBM Software Hub project instance.
Status
Optional.
Syntax
--project-id=<project-id>
Default value
No default.
Valid values
A valid project identifier.
--quiet Suppress verbose messages.
Status
Optional.
Syntax
--quiet
Default value
No default.
Valid values
Not applicable.
--raw-output When set to true, single values are not surrounded by quotation marks in
 JSON output mode.
Status
Optional.
Syntax
--raw-output=true|false
Default value
false
Valid values
false
Single values in JSON output mode are surrounded by quotation marks.
true
Single values in JSON output mode are not surrounded by quotation marks.
--space-id Specify a space identifier.
Status
Optional.
Syntax
--space-id=<space-identifier>
Default value
No default.
Valid values
A valid space identifier.
--verbose Logs include more detailed messages.
Status
Optional.
Syntax
--verbose
Default value
No default.
Valid values
Not applicable.

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.
Define the environment variables.
Replace the following properties with your data.
export ASSET_METADATA= = '''
{
      "name": "connected-data-asset",
      "asset_type": "data_asset",
      "origin_country": "us",
      "asset_category": "USER"
}
'''
export ASSET_ENTITY = '''
{
        "data_asset": {      
            "mime_type": "text/csv",
            "dataset": false
        }
}
'''
export ATTACHMENTS = '''
[
        {
            "asset_type": "data_asset",
            "connection_id": "replace_with_connection_id",
            "connection_path": "CONNUSER/product.csv"
        }
]
'''
export OUTPUT_TYPE=<The output format ('json', 'yaml', or 'text')>
Create a connected data asset.
cpd-cli asset data-asset create \
--attachments=${ATTACHMENTS} \
--entity=${ASSET_ENTITY}
--metadata=${ASSET_METADATA} \
--output=${OUTPUT_TYPE} \
--project-id=${PROJECT_CPD_INST_OPERANDS}