environment create
Create an environment.
Syntax
cpd-cli environment create \
[--authorization-variables=<environment-authorization-variables>] \
[--compute-specification=<environment-compute-specification>] \
[--context=<catalog-project-or-space-id>] \
[--cpd-config=<cpd-config-location>] \
[--cpd-scope=<cpd-config-location>] \
[--description=<environment-description>] \
--display-name=<environment-display-name> \
[--environment-variables=<environment-variables>] \
--hardware-specification=<hardware-sub-specification-pointer> \
[--jmes-query=<jmespath-query>] \
[--location=<environment-runtime-location>] \
--name=<environment-name> \
[--output=json|yaml|table] \
[--output-file=<output-file-location>] \
--profile=<cpd-configuration-profile-name> \
[--project-id=<cpd-project-id>] \
[--quiet] \
[--runtime-definition=<environment-runtime-definition>] \
[--runtime-idle-time=<runtime-idle-timeout-value>] \
--software-specification=<software-sub-specification> \
[--space-id=<space-identifier>] \
[--tools-specification=<environment-tools-specification>] \
--type=<environment-type> \
[--verbose]
Arguments
The environment create
command has
no arguments.
Options
Option | Description |
---|---|
--authorization-variables |
Specify the environment authorization variables.
|
--compute-specification |
Specify the environment compute specification.
|
--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 an environment description.
|
--display-name |
Specify the environment display name.
|
--environment-variables |
Specify environment variables for the specified environment.
|
--hardware-specification |
Provide a pointer to a sub-specification that was defined elsewhere.
|
|
Display command
help.
|
--jmes-query |
The Lucene
query.
|
--location |
Specify the environment runtime location.
|
--name |
Specify the environment 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.
|
--runtime-definition |
Specify the environment's runtime definition.
|
--runtime-idle-time |
Specify the runtime idle timeout value.
|
--software-specification |
Specify a sub-software specification that was defined elsewhere.
|
--space-id |
Specify a space identifier.
|
--tools-specification |
Specify the environment's tools specification.
|
--type |
Specify the environment 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.
-
custom_sw_spec_json = <The sub-software specification> env_name = <The environment display name> hw_spec_json = <A hardware json sub-specification> project_id = <The Cloud Pak for Data project instance> tool_spec_json = <The environment tools json specification>
- Add a package extension to a custom software specification.
-
cpd-cli environment create \ --display-name=${env_name} \ --hardware-specification=${hw_spec_json} \ --jmes-query="metadata.asset_id" \ --name=${env_name} \ --output=json \ --project-id=${PROJECT_CPD_INSTANCE} \ --raw-output \ --software-specification=${custom_sw_spec_json} \ --tools-specification=${tool_spec_json} \ --type=notebook