asset file upload
Upload bytes into the file, with the provided file name, by using the HTTP multi-part format. The command creates a file if the file is missing or overrides the existing file except when override=false.
Extended description
Projects in Cloud Pak for Data
have the following directory structure.
/projects
/projects/<cpd-project-id>
/projects/<cpd-project-id>/project
/projects/<cpd-project-id>/project/readme.json
/projects/<cpd-project-id>/assets
/projects/<cpd-project-id>/assets/ <project assets>
The asset file upload
command can upload files to the
/projects/<cpd-project-id>/assets
folder only.
Syntax
cpd-cli asset file upload \
[--account-id=<catalog-id>] \
[--catalog-id=<catalog-id>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-scope>] \
[--ensure-dir=true|false] \
[--file=<upload-file-path>] \
[--file-content-type=<file-content-type>] \
[--inflate=true|false] \
[--jmes-query=<jmespath-query>] \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
[--override=true|false] \
--path=<asset-file-path> \
--profile=<cpd-profile-name> \
[--project-id=<cpd-project-id>] \
[--quiet] \
[--raw-output=true|false] \
[--root=true|false] \
[--signature=<signed-string>] \
[--space-id=<space-identifier>] \
[--verbose]
Arguments
The asset file upload
command has
no arguments.
Options
Table 1: Command options
Option | Description |
---|---|
--account-id |
Specify the catalog ID that the
file is associated with. A catalog, project, or space ID must also be
specified.
|
--catalog-id |
Specify either a catalog ID,
project ID, or space ID (specify one only).
|
--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.
|
--ensure-dir |
When set to true, the override
utility option ensures that the directory that is specified in the path exists. 201 is returned when
the
path is created. 200 is returned when the path exists. 409 is returned when the path is not a
directory. The option takes precedence over other query options
except
'--inflate'.
|
--file |
Specify the path and name of the
file to upload.
|
--file-content-type |
Specify the file content
type.
|
|
Display command
help.
|
--inflate |
When set to true, the option
takes the supplied file and decompresses it into the target directory. The option is acceptable
only
for project, space, and catalog targets and takes precedence over any other options. The root
directory must exist.
|
--jmes-query |
The Lucene
query.
|
--output |
Specify an output
format.
|
--output-file |
Specify a file path where all
output is redirected.
|
--override |
When set to true, the specified
file is overwritten.
|
--path |
Specify the asset file
path.
|
--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
are not surrounded by quotation marks in
JSON output
mode.
|
--root |
When set to true, the API return
is relative to the target container's root directory instead of the assets directory. The option is
supported for services and for account administrators when targeting the account
directory.
|
--signature |
Specify the signed string
that is obtained by making an API request to the signing endpoint (this is an additional
authorization method).
|
--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.
- Define the environment variables.
-
export FILE=<The *.zip file name in the storage that is associated with the deployment space> export PATH=<The path of the *.zip file to be uploaded> export SPACE_ID=<The deployment space ID>
- Upload a *.zip file to the storage that is associated with the deployment space.
-
cpd-cli asset file upload \ --file=code_package/${FILE_NAME} \ --path=${PATH} \ --profile=${CPD_PROFILE_NAME} \ --space-id=${SPACE_ID}