environment package-extension create
Create a package extension.
Syntax
cpd-cli environment package-extension create \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-config-location>] \
[--description=<package-extension-description>] \
[--jmes-query=<jmespath-query>] \
--name=<package-extension-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>] \
--type=<package-extension-type> \
[--verbose]
Arguments
The environment package-extension 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 package extension description.
|
|
Display command
help.
|
--jmes-query |
The Lucene
query.
|
--name |
Specify the package extension 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 in
which to create the package extension.
|
--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.
|
--type |
Specify the package extension type.
|
--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.
-
pkg_name = "my_packages"
- Create a package extension.
-
cpd-cli environment package-extension create \ --name=${pkg_name} \ --output=json \ --project-id=${PROJECT_CPD_INSTANCE} \ --type=conda_yml