asset attachment create
Create an attachment.
Syntax
cpd-cli asset attachment create \
--asset-id=<asset-guid> \
--asset-type=<asset-type> \
--profile=<profile-name> \
[--catalog-id=<catalog-id>] \
[--connection-id=<connection-id>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-scope>] \
[--data-partitions=<num-data-partitions>] \
[--description=<description>] \
[--is-partitioned=true|false] \
[--jmes-query=<jmespath-query>] \
[--mime=<mime-type>] \
[--name=<attachment-name>] \
[--object-key=<object-key>] \
[--object-key-is-read-only=true|false] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
[--private-url=true|false] \
[--project-id=<project-id>] \
[--quiet] \
[--raw-output=true|false] \
[--space-id=<space-identifier>] \
[--url=<cpd-web-url>] \
[--user-data=<user-data>] \
[--verbose]
Arguments
The asset attachment create command
has no arguments.
Options
Table 1: Command options
| Option | Description |
|---|---|
--asset-id |
Specify the asset
GUID.
|
--asset-type |
Specify the asset type to use when
resolving paths that include only an asset ID.
|
--catalog-id |
Specify either a catalog ID,
project ID, or space ID (specify one only).
|
--connection-id |
Specify the connection
ID.
|
--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.
|
--data-partitions |
The number of data partitions in
the data source.
|
--description |
Specify an attachment
description.
|
|
|
Display command
help.
|
--is-partitioned |
Whether the data source contains
data partitions.
|
--jmes-query |
Provide a JMESPath query to
customize the output.
|
--mime |
Specify the file content mime
type.
|
--name |
Specify the attachment
name.
|
--object-key |
Specify the attachment object
key.
|
--object-key-is-read-only |
When set to true, the attachment
object key is read-only.
|
--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 IBM Software Hub and your credentials for the
instance.
|
--private-url |
Whether the URL that is specified
by the `--url` option is private.
|
--project-id |
Specify an IBM Software Hub
project instance.
|
--quiet |
Suppress verbose
messages.
|
--raw-output |
When set to true, single values
are not surrounded by quotation marks in
JSON output
mode.
|
--space-id |
Specify a space
identifier.
|
--url |
Specify the IBM Software Hub web
URL. You can determine the IBM Software Hub web URL by running the 'oc get routes' command. You must
add HTTPS protocol to the IBM Software Hub web URL (for example, 'https://<cpd-web-url>').
|
--user-data |
Provide a JSON string option or
specify a JSON file to read from by providing a filepath option that begins with an `@` symbol. For
example, `--user-data=@path/to/file.json`.
|
--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> asset_type = <The asset type> space_id = <The deployment space identifier> - Create an attachment. You must specify either project_id or space_id.
-
cpd-cli asset attachment create \ --asset-id=${asset_id} \ --asset-type=${asset_type} \ --project-id=zen \ --space-id=${space_id}