local
with watsonx Orchestrate Development Edition, or remote
with an account on a production watsonx Orchestrate IBM Cloud or AWS. When you activate an environment, every command other than orchestrate server
and orchestrate chat
is target to that environment, including but not limited to the importing, listing, and removal of agents, tools, and connections.
orchestrate env add
command to create an environment to your local CLI.
orchestrate env activate
command to authenticate against a given environment and target all commands other than orchestrate server
and orchestrate chat
to that environment.
run orchestrate env activate
again. This behavior does not exist in the local environment.orchestrate env list command
to list all environments currently available to your CLI.
By default, you have one known as local
. Your local
environment refers to the watsonx Orchestrate Development Edition server. Others can be added by using the orchestrate env add
command. The currently active environment will be indicated by an indicator saying (active)
at the end of the line.
orchestrate env remove
command to remove an environment from your environment list.
~/.config/orchestrate/config.yaml
. This configuration file records each of your environments as well as which environment is currently active.
~/.cache/orchestrate/credentials.yaml
. This file contains the JWT token from your last env activation used to authenticate with your environment.