identify a dag runner

[kolfild26]

Hi,

I need to identify a user (airflow user) which created a dag run through REST API ⚠️ .
There are some advices in stackoverflow, here for instance. They query owner column from Log table in metadb where event equals "trigger".

ID	dttm	dag_id	task_id	event	execution_date	owner
143130	2022-12-18 02:00:35.189421	test_rest		trigger		admin

Above, admin is an airflow user.

This approach doesn't work in case we trigger a dag through rest api. There is no such event as "trigger" for the dag run created in such a way.
This looks strange as we are passing credentials when calling HTTP request and therefore Airflow "knows" who requested.

So, is there any way to retrieve a dag runner in this particular case ❓

[potiuk]

I think adding a log entry in this case might be a good idea if it is not done today.

[kolfild26]

It doesn't seem to be as easy as it sounds. Airflow stores this in airflow.www.fab_security.sqla.models.User.
But it's unclear for me how to build a bridge between SecurityManager where we can access all user attributes (for instance User.username) and dag_run_endpoint. When I search 'post_dag_run' in all the airflow installation files it only points to some .ts scripts and .yaml file.

/airflow/www/static/js/types/api-generated.ts:108:   post: operations["post_dag_run"];
/airflow/www/static/js/types/api-generated.ts:2613:  post_dag_run: {
/airflow/www/static/js/types/api-generated.ts:4213:  export type PostDagRunVariables = CamelCasedPropertiesDeep<operations['post_dag_run']['parameters']['path'] & operations['post_dag_run']['requestBody']['content']['application/json']>;
/airflow/api_connexion/openapi/v1.yaml:656:          operationId: post_dag_run

So, what we need is to access the logged-in User in dag_run_endpoint.py.
Are there any ideas how to do this?

[kolfild26]

So, what we need is to access the logged-in User in dag_run_endpoint.py.

In other words, to identify who I am, in dag_run_endpoint.py

[kolfild26]

oh, here we have flask.g.user which stores the logged-in user. Seems it's resolved now. I'm just talking with myself here today 😄