---
title: "How to set Airflow variables while creating a dev environment"
description: "How to use command-line to set Airflow variables"
author: "Bartosz Mikulski"
author_bio: "Principal AI Engineer & MLOps Architect. I bridge the gap between \"it works in a notebook\" and \"it works for 200 million users.\""
author_url: https://mikulskibartosz.name
author_linkedin: https://www.linkedin.com/in/mikulskibartosz/
author_github: https://github.com/mikulskibartosz
canonical_url: https://mikulskibartosz.name/set-airflow-variables-in-dev-environment
---

When we setup a development environment with Airflow, it is quite annoying to copy-paste the variables and connections from production. Of course, we cannot copy all of them. We will have to modify some values, but that should not stop us from copying everything else.

This article shows how to use the Airflow command-line to export variables from the production environment and import them in the script that builds your development Airflow instance.

## Export Airflow variables

First, we have to use the `airflow variables export` command to get a JSON file with the production parameters. We must run this command on the server that runs the production Airflow environment!

```bash
airflow variables export prod.json
```

## Prepare dev configuration

After that, we can use `jq` to modify the value that must be different in the dev environment. For example, the following code replaces the "some_field" property with "the_new_value":

```bash
contents="$(jq '.some_field = "the_new_value"' prod.json)" && \
echo "${contents}" > dev.json
```

## Import dev configuration

When we have the development configuration ready, we can load it using `airflow variables import`. To do that, we have to start the Airflow instance and run this command on the server that runs the development Airflow environment. Of course, we also have to copy the files between servers, but that depends on your setup.

```bash
airflow variables export dev.json
```