SpecialistOff.NET / Вопросы / Статьи / Фрагменты кода / Резюме / Метки / Помощь / Файлы
НазадМетки: airflow apache airflow
Airflow exposes an experimental Rest API. It is available through the webserver. Endpoints are available at /api/experimental/. Please note that we expect the endpoint definitions to change.
POST /api/experimental/dags/<DAG_ID>/dag_runsCreates a dag_run for a given dag id.
Trigger DAG with config, example:
curl -X POST \
http://localhost:8080/api/experimental/dags/<DAG_ID>/dag_runs \
-H 'Cache-Control: no-cache' \
-H 'Content-Type: application/json' \
-d '{"conf":"{\"key\":\"value\"}"}'
GET /api/experimental/dags/<DAG_ID>/dag_runsReturns a list of Dag Runs for a specific DAG ID.
GET /api/experimental/dags/<string:dag_id>/dag_runs/<string:execution_date>Returns a JSON with a dag_run’s public instance variables. The format for the <string:execution_date> is expected to be “YYYY-mm-DDTHH:MM:SS”, for example: “2016-11-16T11:34:15”.
GET /api/experimental/testTo check REST API server correct work. Return status ‘OK’.
GET /api/experimental/dags/<DAG_ID>/tasks/<TASK_ID>Returns info for a task.
GET /api/experimental/dags/<DAG_ID>/dag_runs/<string:execution_date>/tasks/<TASK_ID>Returns a JSON with a task instance’s public instance variables. The format for the <string:execution_date> is expected to be “YYYY-mm-DDTHH:MM:SS”, for example: “2016-11-16T11:34:15”.
GET /api/experimental/dags/<DAG_ID>/paused/<string:paused>‘<string:paused>’ must be a ‘true’ to pause a DAG and ‘false’ to unpause.
GET /api/experimental/latest_runsReturns the latest DagRun for each DAG formatted for the UI.
GET /api/experimental/poolsGet all pools.
GET /api/experimental/pools/<string:name>Get pool by a given name.
POST /api/experimental/poolsCreate a pool.
DELETE /api/experimental/pools/<string:name>Delete pool.
For some functions the cli can use the API. To configure the CLI to use the API when available configure as follows:
[cli] api_client = airflow.api.client.json_client endpoint_url = http://<WEBSERVER>:<PORT>
Authentication for the API is handled separately to the Web Authentication. The default is to not require any authentication on the API – i.e. wide open by default. This is not recommended if your Airflow webserver is publicly accessible, and you should probably use the deny all backend:
[api] auth_backend = airflow.api.auth.backend.deny_all
Two “real” methods for authentication are currently supported for the API.
To enabled Password authentication, set the following in the configuration:
[api] auth_backend = airflow.contrib.auth.backends.password_auth
It’s usage is similar to the Password Authentication used for the Web interface.
To enable Kerberos authentication, set the following in the configuration:
[api] auth_backend = airflow.api.auth.backend.kerberos_auth [kerberos] keytab = <KEYTAB>
The Kerberos service is configured as airflow/fully.qualified.domainname@REALM. Make sure this principal exists in the keytab file.