-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Closed
Labels
area:APIAirflow's REST/HTTP APIAirflow's REST/HTTP APIarea:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.kind:featureFeature RequestsFeature Requests
Milestone
Description
Description
According to AIP-90, we'll need the following pages to enable users to respond through the Airflow UI.
1. An input page that allows users to enter
This involves 4 public API
GET /api/v2/hitl-details/{dag_id}/{dag_run_id}/{task_id}andGET /api/v2/hitl-details/{dag_id}/{dag_run_id}/{task_id}/{map_index}: get the details to render on the pages (this API should probably also have the information on whether the input-request has been fulfilled)PATCH /api/v2/hitl-details/{dag_id}/{dag_run_id}/{task_id}andPATCH /api/v2/hitl-details/{dag_id}/{dag_run_id}/{task_id}/{map_index}: after users enter data through the form or click the button, this API should be called, and then it should be disabled as we only accept one input.
2. A page that shows tasks waiting for responses
GET /api/v2/hitl-details
Use case/motivation
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
area:APIAirflow's REST/HTTP APIAirflow's REST/HTTP APIarea:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.kind:featureFeature RequestsFeature Requests
Type
Projects
Status
Done

