For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
The behavior and format of this command differs depending on what Astronomer product you’re using. Use the following tabs to change product contexts.
Astro
APC
Update the configuration for a Deployment on Astro.
To update existing worker queues or to create new queues for an existing Deployment, you must update your Deployment by using the --deployment-file flag to update a Deployment file.
Usage
1
astro deployment update <deployment-id> <flags>
This command is recommended for automated workflows. To run this command in an automated process such as a CI/CD pipeline, you can generate an API token, then specify the ASTRO_API_TOKEN environment variable in the system running the Astro CLI:
A numeric value such as 0.25. This number cannot exceed the values you configured in your Default pod resources in the UI or in your Deployment configuration file.
A numeric value followed by Gi, such as 0.5Gi. This number cannot exceed the values you configured in your Default pod resources in the UI or in your Deployment configuration file.
A valid file path to any YAML or JSON Deployment file
--deployment-name
The name of the Deployment to update. Use as an alternative to <deployment-id>.
Any valid Deployment name
-d,--description
A description of the Deployment
Any string. Multiple-word descriptions should be specified in quotations (")
-m, --development-mode
Whether the Deployment is for development mode only. If set to disable, the Deployment can be considered production for the purposes of Astro support case priority, but development-only features such as hibernation aren’t available. You can’t update this value to enable for existing non-development Deployments. Set to disable by default.
disable or enable
-e,--executor
The executor to use for the Deployment
CeleryExecutor or KubernetesExecutor
-f,--force
Force a Deployment update
None
-n,--name
The Deployment’s name
Any string. Multiple-word descriptions should be specified in quotations.
A numeric value such as 10. This number cannot exceed the values you configured in your Default pod resources in the UI or in your Deployment file configuration file.
A numeric value followed by Gi, such as 20Gi. This number cannot exceed the values you configured in your Default pod resources in the UI or in your Deployment file configuration file.
--scheduler-size
The size of the Scheduler for the Deployment.
Possible values can be small, medium, large, or extra_large. extra_large schedulers require a minimum Astro Runtime version of 9.7.0.
-s,--scheduler-au
The number of AU to allocate towards the Deployment’s Scheduler(s). The default is5.
Integer between 0 and 24
-r,--scheduler-replicas
The number of scheduler replicas for the Deployment. The default is 1.
