Skip to content

[v2-10-test] Fix Building docs CI #48568

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
potiuk merged 1 commit into from
Apr 12, 2025
Merged

[v2-10-test] Fix Building docs CI #48568

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/apache-airflow/core-concepts/overview.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,7 @@ DAGs and tasks, but cannot author DAGs.

The *DAG files* need to be synchronized between all the components that use them - *scheduler*,
*triggerer* and *workers*. The *DAG files* can be synchronized by various mechanisms - typical
ways how DAGs can be synchronized are described in :doc:`helm-chart:manage-dags-files` of our
ways how DAGs can be synchronized are described in :doc:`helm-chart:manage-dag-files` of our
Helm Chart documentation. Helm chart is one of the ways how to deploy Airflow in K8S cluster.

.. image:: ../img/diagram_distributed_airflow_architecture.png
Expand Down
7 changes: 3 additions & 4 deletions docs/apache-airflow/public-airflow-interface.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -342,10 +342,9 @@ You can read more about auth managers and how to write your own in :doc:`core-co
Authentication Backends
-----------------------

Authentication backends can extend the way how Airflow authentication mechanism works. You can find out more
about authentication in :doc:`apache-airflow-providers:core-extensions/auth-backends` that also shows available
Authentication backends implemented in the community providers. In case of authentication backend implemented in a
provider, it is then part of the provider's public interface and not Airflow's.
Authentication backends can extend the way how Airflow authentication mechanism works. Those auth_backends
were available in airflow 2 and has been moved to "FAB" provider authentication backends.
You can read more about authentication backends in :doc:`apache-airflow-providers-fab:index`

Connections
-----------
Expand Down
4 changes: 4 additions & 0 deletions docs/exts/includes/sections-and-options.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,11 @@
{{ "-" * (deprecated_option_name + " (Deprecated)")|length }}

.. deprecated:: {{ since_version }}
{% if new_section_name != "celery" %}
The option has been moved to :ref:`{{ new_section_name }}.{{ new_option_name }} <config:{{ new_section_name }}__{{ new_option_name }}>`
{% else %}
The option has been moved to Celery Provider :doc:`apache-airflow-providers-celery:index`
{% endif %}
{% endfor %}
{% endif %}

Expand Down
1 change: 1 addition & 0 deletions newsfragments/48568.significant.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
The ``core.worker_precheck`` config option is not effective any more. Celery provider uses ``celery.worker_precheck`` config option in celery provider < 3.5.0 and as of 3.5.0 it is not used at all.