Skip to content

Commit

Permalink
Mention exec_config in config precedence section
Browse files Browse the repository at this point in the history
  • Loading branch information
o-nikolas committed Feb 5, 2024
1 parent 1e695d1 commit 2a7cb6b
Showing 1 changed file with 4 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,9 @@ In the case of conflicts, the order of precedence from lowest to highest is:
3. Load any values provided in the RUN_TASK_KWARGS option if one is
provided.

.. note::
``exec_config`` is an optional parameter that can be provided to operators. It is a dictionary type and in the context of the ECS Executor it represents a ``run_task_kwargs`` configuration which is then updated over-top of the ``run_task_kwargs`` specified in Airflow config above (if present). It is a recursive update which essentially applies Python update to each nested dictionary in the configuration. Loosely approximated as: ``run_task_kwargs.update(exec_config)``

Required config options:
~~~~~~~~~~~~~~~~~~~~~~~~

Expand All @@ -88,7 +91,7 @@ Optional config options:

- ASSIGN_PUBLIC_IP - Whether to assign a public IP address to the
containers launched by the ECS executor. Defaults to "False".
- CONN_ID - The Airflow connection (i.e. credentials) used by the ECS
- AWS_CONN_ID - The Airflow connection (i.e. credentials) used by the ECS
executor to make API calls to AWS ECS. Defaults to "aws_default".
- LAUNCH_TYPE - Launch type can either be 'FARGATE' OR 'EC2'. Defaults
to "FARGATE".
Expand Down

0 comments on commit 2a7cb6b

Please sign in to comment.