Description

According to AIP-90, we'll need the following pages to enable users to respond through the Airflow UI, in addition to using the REST API. As it is part of a provider instead of the core airflow, we'll need to figure out a way to decouple it from the core (probably related to AIP-68?)

1. An input page that allows users to enter

This involves two public API (not yet implemented or finalized)

1. GET /hitl/input-requests/{task_instance_id}: 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. POST /hitl/input-requests/{task_instance_id}/response: 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 /hitl/input-requests

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

• I agree to follow this project's Code of Conduct