This is an automated email from the ASF dual-hosted git repository.
jscheffl pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 6da9b0c88a3 Unquote executor airflow.cfg variable to fix #48042
(#48064)
6da9b0c88a3 is described below
commit 6da9b0c88a32b18c4ee449b3740688247d3f7479
Author: Dheeraj Turaga <[email protected]>
AuthorDate: Fri Mar 21 15:49:44 2025 -0500
Unquote executor airflow.cfg variable to fix #48042 (#48064)
When setting the executor in the Airflow configuration file (airflow.cfg),
using executor='LocalExecutor,CeleryExecutor' causes a failure, while using
executor = LocalExecutor,CeleryExecutor works correctly.
closes: #48042
---
airflow-core/docs/core-concepts/executor/index.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/airflow-core/docs/core-concepts/executor/index.rst
b/airflow-core/docs/core-concepts/executor/index.rst
index af9d205e509..821ec2f391f 100644
--- a/airflow-core/docs/core-concepts/executor/index.rst
+++ b/airflow-core/docs/core-concepts/executor/index.rst
@@ -130,17 +130,17 @@ Some examples of valid multiple executor configuration:
.. code-block:: ini
[core]
- executor = 'LocalExecutor'
+ executor = LocalExecutor
.. code-block:: ini
[core]
- executor = 'LocalExecutor,CeleryExecutor'
+ executor = LocalExecutor,CeleryExecutor
.. code-block:: ini
[core]
- executor = 'KubernetesExecutor,my.custom.module.ExecutorClass'
+ executor = KubernetesExecutor,my.custom.module.ExecutorClass
.. note::
@@ -151,7 +151,7 @@ To make it easier to specify executors on tasks and dags,
executor configuration
.. code-block:: ini
[core]
- executor = 'LocalExecutor,ShortName:my.custom.module.ExecutorClass'
+ executor = LocalExecutor,ShortName:my.custom.module.ExecutorClass
.. note::
If a DAG specifies a task to use an executor that is not configured, the
DAG will fail to parse and a warning dialog will be shown in the Airflow UI.
Please ensure that all executors you wish to use are specified in Airflow
configuration on *any* host/container that is running an Airflow component
(scheduler, workers, etc).