For a given Deployment on Astro, list its running environment variables in your terminal. To test these environment variables locally without having to manually copy them, you can also use this command to save them in a local
If an existing
.env file already exists in your current directory,
--save will append environment variables to the bottom of that file. It will not override or replace its contents. If
.env does not exist,
--save will create the file for you.
If an environment variable value is set as secret, the CLI will list only its key.
astro deployment variable list
To run this command in an automated process such as a CI/CD pipeline, set the following OS-level environment variables in a way that the Astro CLI can access them:
After setting the variables, this command works for a Deployment without you having to manually authenticate to Astronomer. Astronomer recommends storing
ASTRONOMER_KEY_SECRET as a secret before using it to programmatically update production-level Deployments.
|The Deployment for which to list environment variables||Any valid Deployment ID|
|The directory where a ||Any valid filepath|
|List only the environment variable associated with this key. If not specified, all environment variables are listed||Any string|
|Save environment variables to a local ||``|
|List environment variables for a Deployment that is not in your current Workspace. If not specified, your current Workspace is assumed||Any valid Workspace ID|
# Save all environment variables currently running on an Astro Deployment to the `.env` file in your current directory
$ astro deployment variable list --deployment-id cl03oiq7d80402nwn7fsl3dmv --save
# Save only a single environment variable from a Deployment on Astro to a `.env` file that is outside of your current directory
$ astro deployment variable list --deployment-id cl03oiq7d80402nwn7fsl3dmv --key AIRFLOW__CORE__PARALLELISM --save --env /users/documents/my-astro-project/.env