astro deployment update

Update the configuration for a Deployment on Astro.

Usage​

astro deployment update <deployment-id> <flags>

export ASTRO_API_TOKEN=<your-token>

Options​

| | --deployment-file | A location of the Deployment file to update the Deployment with. The file format can be JSON or YAML. See Create a Deployment with a Deployment 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. | | --resource-quota-cpu | (Astro Hosted only) The Deployment's CPU resource quota for Kubernetes Pods. See Customize a task's Kubernetes Pod for more information. | 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. | | --resource-quota-memory | (Astro Hosted only) The Deployment's memory resource quota for Kubernetes Pods in Gi. See Customize a task's Kubernetes Pod for more information. | 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. | Integer between 0 and 4 | | --workload-identity | The workload identity to use for the Deployment. You must use this flag with --cloud-provider. | A valid AWS, GCP, or Azure arn. | | -w,--workspace-id | Specify a Workspace to update a Deployment outside of your current Workspace | Any valid Workspace ID |

Examples​

# Update a Deployment's name and description
$ astro deployment update cl03oiq7d80402nwn7fsl3dmv -d="My Deployment Description" --name="My Deployment Name"

# Force update a Deployment
$ astro deployment update cl03oiq7d80402nwn7fsl3dmv -d="My Deployment Description" --force

# Update the Deployment according to the configurations specified in the YAML Deployment file
$ astro deployment update --deployment-file deployment.yaml

Create a Deployment on Astronomer Software. This command is functionally identical to using the Software UI to create a Deployment.

Usage​

astro deployment update <deployment-id>

Options​

Examples​

$ astro deployment update telescopic-sky-4599 --executor kubernetes
# Change the executor for a Deployment

$ astro deployment update telescopic-sky-4599 -l="My Deployment label" --workspace-id="ckwqkz36200140ror6axh8p19"
# Update a Deployment in a separate Workspace. The CLI will not prompt you for more information