From 28a3df75e23f62cf4a6edcc07aa405dc5930679e Mon Sep 17 00:00:00 2001
From: Bitnami Bot <containers-bot@bitnami.com>
Date: Tue, 12 Apr 2022 18:18:43 +0000
Subject: [PATCH] 2.2.5-debian-10-r7 release

---
 .../rootfs/opt/bitnami/scripts/airflow-scheduler-env.sh       | 4 ++--
 bitnami/airflow-scheduler/README.md                           | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/bitnami/airflow-scheduler/2/debian-10/rootfs/opt/bitnami/scripts/airflow-scheduler-env.sh b/bitnami/airflow-scheduler/2/debian-10/rootfs/opt/bitnami/scripts/airflow-scheduler-env.sh
index 04c5c41409c0..f93e19d05fd7 100644
--- a/bitnami/airflow-scheduler/2/debian-10/rootfs/opt/bitnami/scripts/airflow-scheduler-env.sh
+++ b/bitnami/airflow-scheduler/2/debian-10/rootfs/opt/bitnami/scripts/airflow-scheduler-env.sh
@@ -38,9 +38,9 @@ airflow_scheduler_env_vars=(
     AIRFLOW_REDIS_USE_SSL
     REDIS_HOST
     REDIS_PORT_NUMBER
-    REDIS_DATABASE
     REDIS_USER
     REDIS_PASSWORD
+    REDIS_DATABASE
 )
 for env_var in "${airflow_scheduler_env_vars[@]}"; do
     file_env_var="${env_var}_FILE"
@@ -90,8 +90,8 @@ export AIRFLOW_DATABASE_USE_SSL="${AIRFLOW_DATABASE_USE_SSL:-no}"
 export AIRFLOW_REDIS_USE_SSL="${AIRFLOW_REDIS_USE_SSL:-no}"
 export REDIS_HOST="${REDIS_HOST:-redis}"
 export REDIS_PORT_NUMBER="${REDIS_PORT_NUMBER:-6379}"
-export REDIS_DATABASE="${REDIS_DATABASE:-1}"
 export REDIS_USER="${REDIS_USER:-}"
 export REDIS_PASSWORD="${REDIS_PASSWORD:-}"
+export REDIS_DATABASE="${REDIS_DATABASE:-1}"
 
 # Custom environment variables may be defined below
diff --git a/bitnami/airflow-scheduler/README.md b/bitnami/airflow-scheduler/README.md
index 94c3f5c822cd..778641859580 100644
--- a/bitnami/airflow-scheduler/README.md
+++ b/bitnami/airflow-scheduler/README.md
@@ -37,7 +37,7 @@ You can find the default credentials and available configuration options in the
 Learn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://docs.bitnami.com/tutorials/understand-rolling-tags-containers/).
 
 
-* [`2`, `2-debian-10`, `2.2.5`, `2.2.5-debian-10-r6`, `latest` (2/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-airflow-scheduler/blob/2.2.5-debian-10-r6/2/debian-10/Dockerfile)
+* [`2`, `2-debian-10`, `2.2.5`, `2.2.5-debian-10-r7`, `latest` (2/debian-10/Dockerfile)](https://github.com/bitnami/bitnami-docker-airflow-scheduler/blob/2.2.5-debian-10-r7/2/debian-10/Dockerfile)
 
 Subscribe to project updates by watching the [bitnami/airflow GitHub repo](https://github.com/bitnami/bitnami-docker-airflow-scheduler).
 
@@ -315,9 +315,9 @@ The Apache Airflow Scheduler instance can be customized by specifying environmen
 - `AIRFLOW_REDIS_USE_SSL`: Set to yes if Redis(TM) uses SSL. Default: **no**
 - `REDIS_HOST`: Hostname for Redis(TM) server. Default: **redis**
 - `REDIS_PORT_NUMBER`: Port used by Redis(TM) server. Default: **6379**
-- `REDIS_DATABASE`: Database number for Redis(TM) server. Default: **1**
 - `REDIS_USER`: USER that Apache Airflow Scheduler will use to connect with Redis(TM). No defaults.
 - `REDIS_PASSWORD`: Password that Apache Airflow Scheduler will use to connect with Redis(TM). No defaults.
+- `REDIS_DATABASE`: Database number for Redis(TM) server. Default: **1**
 
 > In addition to the previous environment variables, all the parameters from the configuration file can be overwritten by using environment variables with this format: `AIRFLOW__{SECTION}__{KEY}`. Note the double underscores.