Skip to main content

Using the BashOperator

The BashOperator is one of the most commonly used operators in Airflow. It executes bash commands or a bash script from within your Airflow DAG.

In this guide you'll learn:

  • When to use the BashOperator.
  • How to use the BashOperator.
  • How to use the BashOperator including executing bash commands and bash scripts.
  • How to run scripts in non-Python programming languages using the BashOperator.

Assumed knowledge

To get the most out of this guide, you should have an understanding of:

How to use the BashOperator

The BashOperator is part of core Airflow and can be used to execute a single bash command, a set of bash commands or a bash script ending in .sh.

The following parameters can be provided to the operator:

  • bash_command: Defines a single bash command, a set of commands, or a bash script to execute. This parameter is required.
  • env: Defines environment variables in a dictionary for the bash process. By default, the defined dictionary overwrites all existing environment variables in your Airflow environment, including those not defined in the provided dictionary. To change this behavior, you can set the append_env parameter. If you leave this parameter blank, the BashOperator inherits the environment variables from your Airflow environment.
  • append_env: Changes the behavior of the env parameter. If you set this to True, the environment variables you define in env are appended to existing environment variables instead of overwriting them. The default is False.
  • output_encoding: Defines the output encoding of the bash command. The default is utf-8.
  • skip_exit_code: Defines which bash exit code should cause the BashOperator to enter a skipped state. The default is 99.
  • cwd: Changes the working directory where the bash command is run. The default is None and the bash command runs in a temporary directory.

The behavior of a BashOperator task is based on the status of the bash shell:

  • Tasks succeed if the whole shell exits with an exit code of 0.
  • Tasks are skipped if the exit code is 99 (unless otherwise specified in skip_exit_code).
  • Tasks fail in case of all other exit codes.

If you expect a non-zero exit from a sub-command you can add the prefix set -e; to your bash command to make sure that the exit is captured as a task failure.

Both the bash_command and the env parameter can accept Jinja templates. However, the input given through Jinja templates to bash_command is not escaped or sanitized. If you are concerned about potentially harmful user input you can use the setup shown in the BashOperator documentation.

When to use the BashOperator

The following are common use cases for the BashOperator in Airflow DAGs:

  • Running a single or multiple bash commands in your Airflow environment.
  • Running a previously prepared bash script.
  • Running scripts in a programming language other than Python.
  • Running commands to initialize tools that lack specific operator support. For example Soda Core.

Example: Execute two bash commands using one BashOperator

The BashOperator can execute any number of bash commands separated by &&.

In this example, you run two bash commands in a single task:

  • echo Hello $MY_NAME! prints the environment variable MY_NAME to the console.
  • echo $A_LARGE_NUMBER | rev 2>&1 | tee $AIRFLOW_HOME/include/my_secret_number.txt takes the environment variable A_LARGE_NUMBER, pipes it to the rev command which reverses any input, and saves the result in a file called my_secret_number.txt located in the /include directory. The reversed number will also be printed to the console.

The second command uses an environment variable from the Airflow environment, AIRFLOW_HOME. This is only possible because append_env is set to True.

from airflow import DAG
from airflow.operators.bash import BashOperator
from datetime import datetime
import os

with DAG(
) as dag:

say_hello_and_create_a_sectet_number = BashOperator(
bash_command="echo Hello $MY_NAME! && echo $A_LARGE_NUMBER | rev 2>&1\
| tee $AIRFLOW_HOME/include/my_secret_number.txt",
"MY_NAME": "<my name>",
"A_LARGE_NUMBER": "231942"

It is also possible to use two separate BashOperators to run the two commands, which can be useful if you want to assign different dependencies to the tasks.

Example: Execute a bash script

The BashOperator can also be provided with a bash script (ending in .sh) to be executed.

For this example, you run a bash script which iterates over all files in the /include folder and prints their names to the console.


echo "The script is starting!"
echo "The current user is $(whoami)"
files = $AIRFLOW_HOME/include/*

for file in $files
echo "The include folder contains $(basename $file)"

echo "The script has run. Have an amazing day!"

Make sure that your bash script ( in this example) is available to your Airflow environment. If you use the Astro CLI, you can make this file accessible to Airflow by placing it in the /include directory of your Astro project.

It is important to make the bash script executable by running the following command before making the script available to your Airflow environment:

chmod +x

If you use the Astro CLI, you can run this command before running astro dev start, or you can add the command to your project's Dockerfile with the following RUN command:

RUN chmod +x /usr/local/airflow/include/

Astronomer recommends running this command in your Dockerfile for production builds such as Astro Deployments or in production CI/CD pipelines.

After making the script available to Airflow, you only have to provide the path to the script in the bash_command parameter. Be sure to add a space character at the end of the filepath, or else the task will fail with a Jinja exception!

from airflow import DAG
from airflow.operators.bash import BashOperator
from datetime import datetime
import os

with DAG(
) as dag:

execute_my_script = BashOperator(
# Note the space at the end of the command!
bash_command="$AIRFLOW_HOME/include/ "
# since the env argument is not specified, this instance of the
# BashOperator has access to the environment variables of the Airflow
# instance like AIRFLOW_HOME

Example: Run a script in another programming language

Using the BashOperator is a straightforward way to run a script in a non-Python programming language in Airflow. You can run a script in any language that can be run with a bash command.

In this example, you run some JavaScript to query a public API providing the current location of the international Space Station. The query result is pushed to XCom so that a second task can extract the latitude and longitude information in a script written in R and print the data to the console.

The following setup is required:

  • Install the JavaScript and R language packages at the OS level.
  • Write a JavaScript file.
  • Write a R script file.
  • Make the scripts available to the Airflow environment.
  • Execute the files from within a DAG using the BashOperator.

If you use the Astro CLI, the programming language packages can be installed at the OS level by adding them to the packages.txt file of your Astro project.


The following JavaScript file contains code for sending a GET request to the /iss-now path at and returning the results to stdout, which will both be printed to the console and pushed to XCom by the BashOperator.

// specify that a http API is queried
const http = require('http');

// define the API to query
const options = {
hostname: '',
port: 80,
path: '/iss-now',
method: 'GET',

const req = http.request(options, res => {
// log the status code of the API response
console.log(`statusCode: ${res.statusCode}`);

// write the result of the GET request to stdout
res.on('data', d => {

// in case of an error print the error statement to the console
req.on('error', error => {


The second task runs a script written in R that uses a regex to filter and print the longitude and latitude information from the API response.

# print outputs to the console
options(echo = TRUE)

# read an argument provided to the R script from the command line
myargs <- commandArgs(trailingOnly = TRUE)

# split a string using : as a separator
set <- strsplit(myargs, ":")

# use regex to extract the lat/long information and convert them to numeric
longitude <- as.numeric(gsub(".*?([0-9]+.[0-9]+).*", "\\1", set[3]))
latitude <- as.numeric(gsub(".*?([0-9]+.[0-9]+).*", "\\1", set[5]))

# print lat/long information in a sentence.
sprintf("The current ISS location: lat: %s / long: %s.", latitude, longitude)

To run these scripts using the BashOperator, ensure that they are accessible to your Airflow environment. If you use the Astro CLI, you can place these files in the /include directory of your Astro project.

The DAG uses the BashOperator to execute both files defined above sequentially.

from airflow import DAG
from airflow.operators.bash import BashOperator
from datetime import datetime

with DAG(
) as dag:

# Use the node command to execute the JavaScript file from the command line
get_ISS_coordinates = BashOperator(
bash_command="node $AIRFLOW_HOME/include/my_java_script.js"

# Use the Rscript command to execute the R file which is being provided
# with the result from task one via an environment variable via XComs
print_ISS_coordinates = BashOperator(
bash_command="Rscript $AIRFLOW_HOME/include/my_R_script.R $ISS_COORDINATES",
"ISS_COORDINATES": "{{ task_instance.xcom_pull(\
task_ids='get_ISS_coordinates', \
key='return_value') }}"
# set append_env to True to be able to use env variables
# like AIRFLOW_HOME from the Airflow environment

get_ISS_coordinates >> print_ISS_coordinates

The logs from the second task include a statement with the current ISS location:

[2022-08-10, 18:54:30 UTC] {} INFO - [1] "The current ISS location: lat: 23.0801 / long: 163.5282."