Skip to content

UI for Human in the loop operators #52094

@Lee-W

Description

@Lee-W

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

Image

This involves 4 public API

  1. GET /api/v2/hitl-details/{dag_id}/{dag_run_id}/{task_id} and GET /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)
  2. PATCH /api/v2/hitl-details/{dag_id}/{dag_run_id}/{task_id} and PATCH /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

  1. GET /api/v2/hitl-details

Image

Use case/motivation

AIP-90

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

Labels

area:APIAirflow's REST/HTTP APIarea:UIRelated to UI/UX. For Frontend Developers.kind:featureFeature Requests

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions