amoghrajesh commented on code in PR #66073: URL: https://github.com/apache/airflow/pull/66073#discussion_r3173283797
########## airflow-core/src/airflow/api_fastapi/execution_api/routes/__init__.py: ########## @@ -52,5 +54,7 @@ authenticated_router.include_router(variables.router, prefix="/variables", tags=["Variables"]) authenticated_router.include_router(xcoms.router, prefix="/xcoms", tags=["XComs"]) authenticated_router.include_router(hitl.router, prefix="/hitlDetails", tags=["Human in the Loop"]) +authenticated_router.include_router(task_state.router, prefix="/state/ti", tags=["Task State"]) +authenticated_router.include_router(asset_state.router, prefix="/state/asset", tags=["Asset State"]) Review Comment: You are right on consistency grounds. As I understand it, technically new endpoints won't break old clients that don't know about them right? ie: old task-sdk workers have no code to call task_state or asset_state APIs. But in any case, updating cadwyn migration rules as a record of what was introduced when is good practice and aligns with how we have done it before, so adding it. -- 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]
