zachliu commented on issue #56103: URL: https://github.com/apache/airflow/issues/56103#issuecomment-3434058102
@phanikumv sadly no updates on my side. this seems to be much more involved than i initially thought. here is what i found so far: in airflow 2.10.5, there is a `set_task_group_state` in the `airflow/models/dag.py`. it is used by two api endpoints `/failed` and `/success`. whether it's a dry run or not is determined by the `commit` argument. this behavior is still in 3.1.x. but we still need to: 1. write a new `set_task_group_state` method in `airflow-core/src/airflow/serialization/serialized_objects.py` 2. create two new api routes (regular & dry_run) in `airflow-core/src/airflow/api_fastapi/core_api/routes/public/task_instances.py` that use the method created in step 1 3. define two corresponding ts methods in `airflow-core/src/airflow/ui/openapi-gen/requests/services.gen.ts` pointing to the new api routes created in step 2 4. create new queries in `airflow-core/src/airflow/ui/src/queries/` using the new methods created in step 3 5. create the `MarkGroupTaskInstanceAsDialog.tsx` and `MarkTaskInstanceAsButton.tsx` in `airflow-core/src/airflow/ui/src/components/MarkAs/TaskInstance` using the new queries created in step 4 6. add the button in `airflow-core/src/airflow/ui/src/pages/GroupTaskInstance/Header.tsx` i'd appreciate if someone could verify these steps. to me it's like a 🐰 🕳️. better get some pointers before jumping in -- 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]
