This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 7fc3cc55cfc Remove note about endpoint migration (#49767)
7fc3cc55cfc is described below
commit 7fc3cc55cfc038f2c8609e5681fe41b08eb639dd
Author: Pierre Jeambrun <[email protected]>
AuthorDate: Fri Apr 25 12:19:18 2025 +0200
Remove note about endpoint migration (#49767)
---
contributing-docs/16_adding_api_endpoints.rst | 8 --------
1 file changed, 8 deletions(-)
diff --git a/contributing-docs/16_adding_api_endpoints.rst
b/contributing-docs/16_adding_api_endpoints.rst
index 02d2940b418..3713921e4a5 100644
--- a/contributing-docs/16_adding_api_endpoints.rst
+++ b/contributing-docs/16_adding_api_endpoints.rst
@@ -101,14 +101,6 @@ These models are defined to structure and validate the
data handled by the API.
After adding or modifying Pydantic models, make sure to run the pre-commit
hooks again to update any generated files.
-Situational: Legacy Endpoint Migration
---------------------------------------
-When migrating legacy endpoint to the new FastAPI API:
-
-1. Implement a feature complete endpoint in comparison to the legacy one or
explain why this is not possible in your context.
-2. Make sure to have a good test coverage by copying over the legacy test
cases to the new endpoint. This will guarantee an isofunctional new endpoint.
-3. Mark the legacy endpoint with the ``@mark_fastapi_migration_done``
decorator. This will help maintainers keep track of the endpoints remaining for
the migration and those already migrated.
-
------
If you happen to change architecture of Airflow, you can learn how we create
our `Architecture diagrams <17_architecture_diagrams.rst>`__.
