feat: Add owner_links field to DAGDetailsResponse by choo121600 · Pull Request #50557 · apache/airflow

choo121600 · 2025-05-13T17:57:38Z

This PR adds the owner_links field to the DAGDetailsResponse object from api_fastapi/core_api in order to resolve#48562

When the UI was based on Flask AppBuilder (FAB), we could retrieve the owner link using the following method:

{% if owner_links and owner.strip() in owner_links.get(dag.dag_id, {}) %}

However, now that the UI has been changed to React, this method no longer works. In the React UI, we need to retrieve the owner_links data from the API, which is why it needed to be included in the DAGDetailsResponse.

In the current implementation, owner_links is stored as a dictionary like:

{ "owner_example": "https://example_link.com" }

I have preserved this format and added the owner_links field to the DAGDetailsResponse. This allows the UI to receive and render the owner_links data via the API response.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…lated schemas

pierrejeambrun

Thanks

github-actions · 2025-05-14T13:13:27Z

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker e37a40d v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d)

pierrejeambrun · 2025-05-14T13:24:05Z

Manual cherry pick PR here:
#50604

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d) Co-authored-by: Yeonguk <choo121600@gmail.com>

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py

choo121600 · 2025-05-13T17:57:38Z

This PR adds the owner_links field to the DAGDetailsResponse object from api_fastapi/core_api in order to resolve#48562

When the UI was based on Flask AppBuilder (FAB), we could retrieve the owner link using the following method:

{% if owner_links and owner.strip() in owner_links.get(dag.dag_id, {}) %}

However, now that the UI has been changed to React, this method no longer works. In the React UI, we need to retrieve the owner_links data from the API, which is why it needed to be included in the DAGDetailsResponse.

In the current implementation, owner_links is stored as a dictionary like:

{ "owner_example": "https://example_link.com" }

I have preserved this format and added the owner_links field to the DAGDetailsResponse. This allows the UI to receive and render the owner_links data via the API response.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…lated schemas

pierrejeambrun

Thanks

github-actions · 2025-05-14T13:13:27Z

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker e37a40d v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d)

pierrejeambrun · 2025-05-14T13:24:05Z

Manual cherry pick PR here:
#50604

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d) Co-authored-by: Yeonguk <choo121600@gmail.com>

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py

choo121600 · 2025-05-13T17:57:38Z

This PR adds the owner_links field to the DAGDetailsResponse object from api_fastapi/core_api in order to resolve#48562

When the UI was based on Flask AppBuilder (FAB), we could retrieve the owner link using the following method:

{% if owner_links and owner.strip() in owner_links.get(dag.dag_id, {}) %}

However, now that the UI has been changed to React, this method no longer works. In the React UI, we need to retrieve the owner_links data from the API, which is why it needed to be included in the DAGDetailsResponse.

In the current implementation, owner_links is stored as a dictionary like:

{ "owner_example": "https://example_link.com" }

I have preserved this format and added the owner_links field to the DAGDetailsResponse. This allows the UI to receive and render the owner_links data via the API response.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…lated schemas

pierrejeambrun

Thanks

github-actions · 2025-05-14T13:13:27Z

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker e37a40d v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d)

pierrejeambrun · 2025-05-14T13:24:05Z

Manual cherry pick PR here:
#50604

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d) Co-authored-by: Yeonguk <choo121600@gmail.com>

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py

choo121600 · 2025-05-13T17:57:38Z

This PR adds the owner_links field to the DAGDetailsResponse object from api_fastapi/core_api in order to resolve#48562

When the UI was based on Flask AppBuilder (FAB), we could retrieve the owner link using the following method:

{% if owner_links and owner.strip() in owner_links.get(dag.dag_id, {}) %}

However, now that the UI has been changed to React, this method no longer works. In the React UI, we need to retrieve the owner_links data from the API, which is why it needed to be included in the DAGDetailsResponse.

In the current implementation, owner_links is stored as a dictionary like:

{ "owner_example": "https://example_link.com" }

I have preserved this format and added the owner_links field to the DAGDetailsResponse. This allows the UI to receive and render the owner_links data via the API response.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…lated schemas

pierrejeambrun

Thanks

github-actions · 2025-05-14T13:13:27Z

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker e37a40d v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d)

pierrejeambrun · 2025-05-14T13:24:05Z

Manual cherry pick PR here:
#50604

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d) Co-authored-by: Yeonguk <choo121600@gmail.com>

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py

choo121600 · 2025-05-13T17:57:38Z

This PR adds the owner_links field to the DAGDetailsResponse object from api_fastapi/core_api in order to resolve#48562

When the UI was based on Flask AppBuilder (FAB), we could retrieve the owner link using the following method:

{% if owner_links and owner.strip() in owner_links.get(dag.dag_id, {}) %}

However, now that the UI has been changed to React, this method no longer works. In the React UI, we need to retrieve the owner_links data from the API, which is why it needed to be included in the DAGDetailsResponse.

In the current implementation, owner_links is stored as a dictionary like:

{ "owner_example": "https://example_link.com" }

I have preserved this format and added the owner_links field to the DAGDetailsResponse. This allows the UI to receive and render the owner_links data via the API response.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…lated schemas

pierrejeambrun

Thanks

github-actions · 2025-05-14T13:13:27Z

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker e37a40d v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d)

pierrejeambrun · 2025-05-14T13:24:05Z

Manual cherry pick PR here:
#50604

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d) Co-authored-by: Yeonguk <choo121600@gmail.com>

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py

choo121600 · 2025-05-13T17:57:38Z

This PR adds the owner_links field to the DAGDetailsResponse object from api_fastapi/core_api in order to resolve#48562

When the UI was based on Flask AppBuilder (FAB), we could retrieve the owner link using the following method:

{% if owner_links and owner.strip() in owner_links.get(dag.dag_id, {}) %}

However, now that the UI has been changed to React, this method no longer works. In the React UI, we need to retrieve the owner_links data from the API, which is why it needed to be included in the DAGDetailsResponse.

In the current implementation, owner_links is stored as a dictionary like:

{ "owner_example": "https://example_link.com" }

I have preserved this format and added the owner_links field to the DAGDetailsResponse. This allows the UI to receive and render the owner_links data via the API response.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…lated schemas

pierrejeambrun

Thanks

github-actions · 2025-05-14T13:13:27Z

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker e37a40d v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d)

pierrejeambrun · 2025-05-14T13:24:05Z

Manual cherry pick PR here:
#50604

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d) Co-authored-by: Yeonguk <choo121600@gmail.com>

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py

choo121600 · 2025-05-13T17:57:38Z

This PR adds the owner_links field to the DAGDetailsResponse object from api_fastapi/core_api in order to resolve#48562

When the UI was based on Flask AppBuilder (FAB), we could retrieve the owner link using the following method:

{% if owner_links and owner.strip() in owner_links.get(dag.dag_id, {}) %}

However, now that the UI has been changed to React, this method no longer works. In the React UI, we need to retrieve the owner_links data from the API, which is why it needed to be included in the DAGDetailsResponse.

In the current implementation, owner_links is stored as a dictionary like:

{ "owner_example": "https://example_link.com" }

I have preserved this format and added the owner_links field to the DAGDetailsResponse. This allows the UI to receive and render the owner_links data via the API response.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…lated schemas

pierrejeambrun

Thanks

github-actions · 2025-05-14T13:13:27Z

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker e37a40d v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d)

pierrejeambrun · 2025-05-14T13:24:05Z

Manual cherry pick PR here:
#50604

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d) Co-authored-by: Yeonguk <choo121600@gmail.com>

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py

choo121600 · 2025-05-13T17:57:38Z

This PR adds the owner_links field to the DAGDetailsResponse object from api_fastapi/core_api in order to resolve#48562

When the UI was based on Flask AppBuilder (FAB), we could retrieve the owner link using the following method:

{% if owner_links and owner.strip() in owner_links.get(dag.dag_id, {}) %}

However, now that the UI has been changed to React, this method no longer works. In the React UI, we need to retrieve the owner_links data from the API, which is why it needed to be included in the DAGDetailsResponse.

In the current implementation, owner_links is stored as a dictionary like:

{ "owner_example": "https://example_link.com" }

I have preserved this format and added the owner_links field to the DAGDetailsResponse. This allows the UI to receive and render the owner_links data via the API response.

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…lated schemas

pierrejeambrun

Thanks

github-actions · 2025-05-14T13:13:27Z

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker e37a40d v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d)

pierrejeambrun · 2025-05-14T13:24:05Z

Manual cherry pick PR here:
#50604

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py (cherry picked from commit e37a40d) Co-authored-by: Yeonguk <choo121600@gmail.com>

* feat: Add owner_links field to DAGDetailsResponse model and update related schemas * remove owner_links in test code * add tests for DAG owner_links in DAG details endpoint * refactor: apply ruff formatting to test_dags.py

feat: Add owner_links field to DAGDetailsResponse model and update re…
83775c9
…lated schemas

choo121600 requested review from bbovenzi, bugraoz93, ephraimbuddy, jason810496, jscheffl, kaxil, pierrejeambrun, potiuk, rawwar, ryanahamilton and shubhamraj-git as code owners May 13, 2025 17:57

boring-cyborgBot added area:airflow-ctl area:API Airflow's REST/HTTP API area:UI Related to UI/UX. For Frontend Developers. labels May 13, 2025

remove owner_links in test code
2fdaa81

bbovenzi approved these changes May 13, 2025
View reviewed changes

bbovenzi added this to the Airflow 3.0.2 milestone May 13, 2025

bbovenzi added the backport-to-v3-0-test label May 13, 2025

choo121600 added 2 commits May 14, 2025 04:35

add tests for DAG owner_links in DAG details endpoint
af841c8

refactor: apply ruff formatting to test_dags.py
2c00444

jason810496 approved these changes May 14, 2025
View reviewed changes

bugraoz93 approved these changes May 14, 2025
View reviewed changes

pierrejeambrun approved these changes May 14, 2025
View reviewed changes

pierrejeambrun merged commit e37a40d into apache:mainMay 14, 2025

kaxil mentioned this pull request Jun 10, 2025
Update Python Client to 3.0.2rc1 apache/airflow-client-python#136
Merged

tirkarthi mentioned this pull request Jul 17, 2025
Revert "docs: remove DAG owner links how-to since no feature parity (#49262)" #53456
Merged