eladkal commented on code in PR #52259: URL: https://github.com/apache/airflow/pull/52259#discussion_r2183444435
########## airflow-core/docs/public-airflow-interface.rst: ########## @@ -28,6 +28,21 @@ and for automating certain aspects of the Airflow workflow. Using Airflow Public Interfaces =============================== +.. note:: + + As of **Airflow 3.0**, users should use the ``airflow.sdk`` namespace as the official **Public Interface**, as defined in `AIP-72 <https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-72+Task+Execution+Interface+aka+Task+SDK>`_. Review Comment: What is the motivation to mention AIP-72? Generally speaking AIP numbering is internal information of Airflow developers they are not so meaningful to users (we do mention them sometimes but mostly for future plans not as reference to completed work) ########## airflow-core/docs/public-airflow-interface.rst: ########## @@ -28,6 +28,21 @@ and for automating certain aspects of the Airflow workflow. Using Airflow Public Interfaces =============================== +.. note:: + + As of **Airflow 3.0**, users should use the ``airflow.sdk`` namespace as the official **Public Interface**, as defined in `AIP-72 <https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-72+Task+Execution+Interface+aka+Task+SDK>`_. + + Direct interaction with internal modules or the metadata database is not possible. + For stable, production-safe integration, it is recommended to use: + + - The official **REST API** + - The **Python Client SDK** (`airflow-client-python`) + - The new **Task SDK** (``airflow.sdk``) + + Related docs: + - `Release Notes 3.0 <https://airflow.apache.org/docs/apache-airflow/stable/release_notes.html>`_ + - `Task SDK Overview <https://airflow.apache.org/docs/apache-airflow/stable/concepts/taskflow.html>`_ Review Comment: should be relative links rather than http ones. We use http only for external resources -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
