deploy
command creates a new agent deployment or updates an existing one. It builds a deployment manifest with the provided parameters and monitors the deployment status until the agent is ready.
If the agent name already exists, you’ll be prompted to confirm the update unless the --force
flag is used.
This command will wait for the active deployment / revision to enter a ready state before returning. If the deployment fails, the command will exit with an error with more information.
Usage
Unique string identifier for the agent deployment. Must not contain spaces.
URL of the Docker image to deploy. Must be a valid Docker image URL. For
example:
docker.io/my-repo/my-image:latest
.Name of the image pull secret to use for accessing private repositories. The
secret must be previously created using the
pcc secrets image-pull-secret
command.Organization to deploy the agent to. If not provided, uses the current
organization from your configuration.
Name of the secret set to use for the deployment. The secret set must exist in
the specified organization.
Minimum number of agent instances to keep warm at all times. Default is 0,
which means the agent will scale down to zero when not in use. Setting this to
1 or higher avoids cold starts.
Maximum number of allowed agent instances. Must be between 1 and 50. If you
need more agents, please contact us at help@daily.co or via
Discord.
Enable Krisp noise cancellation for this deployed agent. In addition, you also
need to enable the
KrispFilter()
for your transport. See the Krisp Noise
Cancellation guide for more information.Force deployment and skip confirmation prompts. Use with caution.
Examples
Deploy a new agent:Configuration TOML
The deploy command will look for any values declared in an adjacentpcc-deploy.toml
file (documented here).
Values are applied with the following order of precedence:
- CLI arguments
pcc-deploy.toml
values- Default values