code-package create
Create a code package in the specified project or space.
Syntax
cpd-cli code-package create \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-config-location>] \
[--description=<description>] \
[--file-reference=<file-reference>] \
[--jmes-query=<jmespath-query>] \
--name=<code-package-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] \
[--space-id=<space-identifier>] \
[--verbose]
Arguments
The code-package create
command has
no arguments.
Options
Option | Description |
---|---|
--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 code package description.
|
--file-reference |
Specify the reference to the file in the object storage.
|
|
Display command
help.
|
--jmes-query |
The Lucene
query.
|
--name |
Specify the code
package 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 profile-name from the Cloud
Pak for Data configuration.
|
--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.
|
--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.
- Specify the environment variables in a script file.
-
CODE_PACKAGE_NAME=<The name of the code package in the deployment space> CODE_PACKAGE_DESCRIPTION=<A description of the code package in the deployment space> FILE_NAME=<The *.zip file name in the storage that is associated with the deployment space> PROFILE=<The Cloud Pak for Data configuration profile name> SPACE_ID=<The deployment space ID>
- Create a code package in the deployment space.
-
cpd-cli asset file upload \ --description=${CODE_PACKAGE_DESCRIPTION} \ --file-reference=code_package/${FILE_NAME} \ --profile=${PROFILE} \ --name=${CODE_PACKAGE_NAME} \ --space-id=${SPACE_ID}