Manage Astronomer production deployments with Astro CLI. Use when the user wants to authenticate, switch workspaces, create/update/delete deployments, or deploy code to production.

Astro Deployment Management This skill helps you manage production Astronomer deployments using the Astro CLI. For local development , see the managing astro local env skill. For production troubleshooting , see the troubleshooting astro deployments skill. Authentication All deployment operations require authentication: Authentication tokens are stored locally for subsequent commands. Run this before any deployment operations. Workspace Management Deployments are organized into workspaces: Workspace context is maintained between sessions. Most deployment commands operate within the current workspace context. List and Inspect Deployments What inspect Shows Deployment status (HEALTHY, UNHEALTHY) Runtime version and Airflow version Executor type (CELERY, KUBERNETES, LOCAL) Scheduler configuration (size, count) Worker queue settings (min/max workers, concurrency, worker type) Resource quotas (CPU, memory) Environment variables Last deployment timestamp and current tag Webserver and API URLs High availability status Create Deployments Update Deployments Delete Deployments Destructive : This cannot be undone. All DAGs, task history, and metadata will be lost. Deploy Code to Production Full Deploy Deploy both DAGs and Docker image (required when dependencies change): Use when: Dependencies changed ( requirements.txt , packages.txt , Dockerfile ) First deployment of new project Significant infrastructure changes DAG Only Deploy (Recommended for Iteration) Deploy only DAG files, skip Docker image rebuild: Use when: Only DAG files changed (Python files in dags/ directory) Quick iteration during development Much faster than full deploy (seconds vs minutes) Requires : dag deploy enabled flag set on deployment (see Update Deployments) Image Only Deploy Deploy only Docker image, skip DAG sync: Use when: Only dependencies changed Dockerfile or requirements updated No DAG changes Force Deploy Bypass safety checks and deploy: Caution : Skips validation that could prevent broken deployments. Deployment API Tokens Manage API tokens for programmatic access to deployments: Roles : DEPLOYMENT ADMIN : Full access to deployment Note : Token value is only shown at creation time. Store it securely. Common Workflows First Time Production Deployment Iterative DAG Development Promoting Code from Staging to Production Configuration Management Tips Use dags flag for fast iteration (seconds vs minutes) Always test in staging workspace before production Use deployment inspect to verify deployment health before deploying Deployment IDs are permanent, names can change Most commands work with deployment ID; inspect also accepts deployment name Set dag deploy enabled once per deployment for fast deploys Keep workspace context visible with astro workspace list (shows asterisk for current) Related Skills troubleshooting astro deployments : Investigate deployment issues, view logs, manage environment variables managing astro local env : Manage local Airflow development environment setting up astro project : Initialize and configure Astro projects

managing-astro-deployments