bamaer opened a new pull request, #9634:
URL: https://github.com/apache/hop/pull/9634

   Fixes #9630.
   
   Adds a **Trigger Airflow DAG run** workflow action and an **Airflow 
Connection** metadata type (`airflow-connection`), in a new plugin 
`plugins/tech/airflow` that ships with the client.
   
   - The connection works with Airflow 3 and its REST API v2. It signs in with 
a username and password (exchanged for a token at `/auth/token`, renewed when 
it expires), with a token, or without credentials. *Test connection* checks the 
credentials as well as the URL.
   - The action starts a DAG run with an optional run id, logical date and run 
conf (a JSON object, a key/value table, or both) and by default waits until the 
run finishes. It fails when the run fails (the log names the failed tasks), 
when the wait times out, or when the DAG does not exist. The run id and state 
go into variables.
   - When the DAG is paused and the action waits, it fails without starting a 
run: the run would stay queued. A status check that fails (API server restart, 
proxy error) is retried at the next check; 5 failures in a row fail the action.
   - The dialog and the editor use grouped annotated widgets.
   - New `HopMetadataPropertyType.AIRFLOW_CONNECTION`, so renaming a connection 
updates the actions that use it.
   - The client uses HTTP/1.1: Airflow's API server answers the HTTP/2 upgrade 
request Java sends by default on `http://` with HTTP 400. It does not follow 
redirects, because Java turns a redirected POST into a GET; the error names the 
address to use instead.
   
   Not included: TLS options. Hop uses the certificates the JVM trusts.
   
   Tests:
   
   - Unit tests for the client and the action (WireMock), UI tests for the 
dialog and the editor.
   - New IT project `integration-tests/airflow` against `apache/airflow:3.4.0` 
(`run-tests-docker.sh PROJECT_NAME=airflow`): 4/4 pass. With the plugin removed 
from the client, all 4 fail.
   


-- 
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]

Reply via email to