potiuk commented on code in PR #28300: URL: https://github.com/apache/airflow/pull/28300#discussion_r1046554283
########## docs/apache-airflow/public-airflow-api.rst: ########## @@ -0,0 +1,141 @@ + .. Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + .. http://www.apache.org/licenses/LICENSE-2.0 + + .. Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + +"Public API" of Airflow +======================= + +The Public API of Apache Airflow is a set of programmatic interfaces that allow developers to interact +with and access certain features of the Apache Airflow system. This can include operations such as +creating and managing DAGs (directed acyclic graphs), managing tasks and their dependencies, +and extending Airflow capabilities by writing new Executors, Plugins, Operators and Providers. The +public API of Apache Airflow can be useful for building custom tools and integrations with other systems, +as well as for automating certain aspects of the Airflow workflow. + +In general, the public API is an important part of the Airflow ecosystem and can be a powerful tool for users +and developers who want to extend the functionality of the system. + +What kind of APIs are Public in Apache Airflow? +=============================================== + +Apache Airflow has a number of different public APIs that allow developers to interact with various +aspects of the system. Some examples of the types of public APIs exposed as Python objects +that are available in Apache Airflow include: + +* :doc:`DAG <concepts/dags>`_ (Directed Acyclic Graph) APIs, which allow developers to create, manage, + and access DAGs in Airflow. +* :doc:`Task <concepts/tasks>`_ APIs, which provide access to information about individual tasks within + a DAG, such as their dependencies and execution status. +* :doc:`Operator <concepts/operators>`_ APIs, which allows the developers to write their custom Operators. +* :doc:`Decorators <howto/create-custom-decorator>`_ APIs, which allows the developers to write their + custom decorators to make it easier to write :doc:`TaskFlow <tutorial/taskflow>`_ DAGs. +* :doc:`Secret Managers <security/secrets>`_ APIs, which allows the developers to write their custom + Secret Managers to safely access credentials and other secret configuration of their workflows. +* :doc:`Connection management <concepts/connections>`_ APIs, which allow developers to manage + connections to external systems +* :doc:`XCom <concepts/xcoms>`_, which allow developers to manage cross-task communication within Airflow. +* :doc:`Variables <concepts/variables>`_, which allow developers to manage variables within Airflow. +* :doc:`Executors <executor/index>`_, which allow developers to manage the execution of tasks within Airflow. +* :doc:`Plugins <plugins>`_, which allow developers to extend internal Airflow capabilities - add new UI + pages, custom :doc:`TimeTables <concepts/timetable>`_, :doc:`Extra Links <howto/define_extra_link>`_, + :doc:`Listeners <listeners>`_ - all of which are considered public APIs. + +Also Airflow has a stable REST API that allows users to interact with Airflow via HTTP requests and a +CLI that allows users to interact with Airflow via command line commands. + +Overall, the public APIs in Apache Airflow are designed to provide developers with a wide +range of tools and capabilities for interacting with the system and extending its functionality. Review Comment: I think it's nice actually. We should not assume the user that comes here has the same assumptions what the public interface is about. having a short (it's short) and explanatory (it is) preamble like that actually sets the tone and provide the context. It explains to the reader, why we explain this all. We already have a random dump of links in various places and they have no explanation why they are there. Yes it's shorter, but I think some form of context that explains what we really want to explain is important here. -- 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]
