This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch v2-10-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v2-10-test by this push:
new b910b10c85e [v2-10-test] Fix Docs Building in 2-10-test (#48568)
b910b10c85e is described below
commit b910b10c85e4a2bf09d09555b78b45dbafa5e3bb
Author: LIU ZHE YOU <[email protected]>
AuthorDate: Sun Apr 13 00:14:42 2025 +0800
[v2-10-test] Fix Docs Building in 2-10-test (#48568)
Some recent changes in main and documentation published in the
inventories, made the 2.10 doc building fail as references to
non-existing docs in the new inventories were still used in the
documentation for 2.10
This PR fixes it by changing the docs to not refer to those
changed docs any more.
The PRs that removed the links: #47320 and #47399
Co-authored-by: Jarek Potiuk <[email protected]>
---
docs/apache-airflow/core-concepts/overview.rst | 2 +-
docs/apache-airflow/public-airflow-interface.rst | 7 +++----
docs/exts/includes/sections-and-options.rst | 4 ++++
newsfragments/48568.significant.rst | 1 +
4 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/docs/apache-airflow/core-concepts/overview.rst
b/docs/apache-airflow/core-concepts/overview.rst
index 767b7e8990f..0a777368d8d 100644
--- a/docs/apache-airflow/core-concepts/overview.rst
+++ b/docs/apache-airflow/core-concepts/overview.rst
@@ -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
diff --git a/docs/apache-airflow/public-airflow-interface.rst
b/docs/apache-airflow/public-airflow-interface.rst
index c960c9c805f..205372f73dc 100644
--- a/docs/apache-airflow/public-airflow-interface.rst
+++ b/docs/apache-airflow/public-airflow-interface.rst
@@ -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
-----------
diff --git a/docs/exts/includes/sections-and-options.rst
b/docs/exts/includes/sections-and-options.rst
index f191cf10d55..8ca1aa4f777 100644
--- a/docs/exts/includes/sections-and-options.rst
+++ b/docs/exts/includes/sections-and-options.rst
@@ -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 %}
diff --git a/newsfragments/48568.significant.rst
b/newsfragments/48568.significant.rst
new file mode 100644
index 00000000000..3d5760a6c8a
--- /dev/null
+++ b/newsfragments/48568.significant.rst
@@ -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.
