Reduce redundant Dag team lookups in authorization checks

[yuseok89]

closes: #61485

requires_access_dag resolves a Dag's owning team via DagModel.get_team_name on every call — twice per grid endpoint (TASK_INSTANCE + RUN) and on every auto-refresh poll.

This caches the lookup with a short per-process TTL.

Other large costs discussed in #61485 have already been addressed by separate PRs. I left the detailed breakdown in the issue comment, and this PR covers the remaining redundant Dag team lookup.

Impact

Team-ownership DB queries per grid page load:

	first load	follow-up poll
before	6	6
after	1	0

Also included

• New config [core] team_name_cache_ttl (default 30s).

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Opus 4.8

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[vincbeck]

CI is failing

[henry3260]

looks good!
test_bulk_delete_query_count_scales_linearly_with_task_count still asserts
the old exact counts, we should update it

[yuseok89]

CI is failing

You're right, sorry. Once it was approved I moved it out of draft, but an approval isn't the same as a green CI, and I should have confirmed that first.

The failure wasn't in the tests this change adds. Caching the Dag team lookup shaves one query off the bulk task-instance delete path, which tripped a pre-existing query-count regression guard there. That's the cross-area interaction I didn't catch. It's now fixed and pushed.

[yuseok89]

closes: #61485

requires_access_dag resolves a Dag's owning team via DagModel.get_team_name on every call — twice per grid endpoint (TASK_INSTANCE + RUN) and on every auto-refresh poll.

This caches the lookup with a short per-process TTL.

Other large costs discussed in #61485 have already been addressed by separate PRs. I left the detailed breakdown in the issue comment, and this PR covers the remaining redundant Dag team lookup.

Impact

Team-ownership DB queries per grid page load:

	first load	follow-up poll
before	6	6
after	1	0

Also included

• New config [core] team_name_cache_ttl (default 30s).

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Opus 4.8

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[vincbeck]

CI is failing

[henry3260]

looks good!
test_bulk_delete_query_count_scales_linearly_with_task_count still asserts
the old exact counts, we should update it

[yuseok89]

CI is failing

You're right, sorry. Once it was approved I moved it out of draft, but an approval isn't the same as a green CI, and I should have confirmed that first.

The failure wasn't in the tests this change adds. Caching the Dag team lookup shaves one query off the bulk task-instance delete path, which tripped a pre-existing query-count regression guard there. That's the cross-area interaction I didn't catch. It's now fixed and pushed.

[yuseok89]

closes: #61485

requires_access_dag resolves a Dag's owning team via DagModel.get_team_name on every call — twice per grid endpoint (TASK_INSTANCE + RUN) and on every auto-refresh poll.

This caches the lookup with a short per-process TTL.

Other large costs discussed in #61485 have already been addressed by separate PRs. I left the detailed breakdown in the issue comment, and this PR covers the remaining redundant Dag team lookup.

Impact

Team-ownership DB queries per grid page load:

	first load	follow-up poll
before	6	6
after	1	0

Also included

• New config [core] team_name_cache_ttl (default 30s).

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Opus 4.8

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[vincbeck]

CI is failing

[henry3260]

looks good!
test_bulk_delete_query_count_scales_linearly_with_task_count still asserts
the old exact counts, we should update it

[yuseok89]

CI is failing

You're right, sorry. Once it was approved I moved it out of draft, but an approval isn't the same as a green CI, and I should have confirmed that first.

The failure wasn't in the tests this change adds. Caching the Dag team lookup shaves one query off the bulk task-instance delete path, which tripped a pre-existing query-count regression guard there. That's the cross-area interaction I didn't catch. It's now fixed and pushed.

[yuseok89]

closes: #61485

requires_access_dag resolves a Dag's owning team via DagModel.get_team_name on every call — twice per grid endpoint (TASK_INSTANCE + RUN) and on every auto-refresh poll.

This caches the lookup with a short per-process TTL.

Other large costs discussed in #61485 have already been addressed by separate PRs. I left the detailed breakdown in the issue comment, and this PR covers the remaining redundant Dag team lookup.

Impact

Team-ownership DB queries per grid page load:

	first load	follow-up poll
before	6	6
after	1	0

Also included

• New config [core] team_name_cache_ttl (default 30s).

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Opus 4.8

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[vincbeck]

CI is failing

[henry3260]

looks good!
test_bulk_delete_query_count_scales_linearly_with_task_count still asserts
the old exact counts, we should update it

[yuseok89]

CI is failing

You're right, sorry. Once it was approved I moved it out of draft, but an approval isn't the same as a green CI, and I should have confirmed that first.

The failure wasn't in the tests this change adds. Caching the Dag team lookup shaves one query off the bulk task-instance delete path, which tripped a pre-existing query-count regression guard there. That's the cross-area interaction I didn't catch. It's now fixed and pushed.

[yuseok89]

closes: #61485

requires_access_dag resolves a Dag's owning team via DagModel.get_team_name on every call — twice per grid endpoint (TASK_INSTANCE + RUN) and on every auto-refresh poll.

This caches the lookup with a short per-process TTL.

Other large costs discussed in #61485 have already been addressed by separate PRs. I left the detailed breakdown in the issue comment, and this PR covers the remaining redundant Dag team lookup.

Impact

Team-ownership DB queries per grid page load:

	first load	follow-up poll
before	6	6
after	1	0

Also included

• New config [core] team_name_cache_ttl (default 30s).

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Opus 4.8

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[vincbeck]

CI is failing

[henry3260]

looks good!
test_bulk_delete_query_count_scales_linearly_with_task_count still asserts
the old exact counts, we should update it

[yuseok89]

CI is failing

You're right, sorry. Once it was approved I moved it out of draft, but an approval isn't the same as a green CI, and I should have confirmed that first.

The failure wasn't in the tests this change adds. Caching the Dag team lookup shaves one query off the bulk task-instance delete path, which tripped a pre-existing query-count regression guard there. That's the cross-area interaction I didn't catch. It's now fixed and pushed.

[yuseok89]

closes: #61485

requires_access_dag resolves a Dag's owning team via DagModel.get_team_name on every call — twice per grid endpoint (TASK_INSTANCE + RUN) and on every auto-refresh poll.

This caches the lookup with a short per-process TTL.

Other large costs discussed in #61485 have already been addressed by separate PRs. I left the detailed breakdown in the issue comment, and this PR covers the remaining redundant Dag team lookup.

Impact

Team-ownership DB queries per grid page load:

	first load	follow-up poll
before	6	6
after	1	0

Also included

• New config [core] team_name_cache_ttl (default 30s).

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Opus 4.8

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[vincbeck]

CI is failing

[henry3260]

looks good!
test_bulk_delete_query_count_scales_linearly_with_task_count still asserts
the old exact counts, we should update it

[yuseok89]

CI is failing

You're right, sorry. Once it was approved I moved it out of draft, but an approval isn't the same as a green CI, and I should have confirmed that first.

The failure wasn't in the tests this change adds. Caching the Dag team lookup shaves one query off the bulk task-instance delete path, which tripped a pre-existing query-count regression guard there. That's the cross-area interaction I didn't catch. It's now fixed and pushed.

[yuseok89]

closes: #61485

requires_access_dag resolves a Dag's owning team via DagModel.get_team_name on every call — twice per grid endpoint (TASK_INSTANCE + RUN) and on every auto-refresh poll.

This caches the lookup with a short per-process TTL.

Other large costs discussed in #61485 have already been addressed by separate PRs. I left the detailed breakdown in the issue comment, and this PR covers the remaining redundant Dag team lookup.

Impact

Team-ownership DB queries per grid page load:

	first load	follow-up poll
before	6	6
after	1	0

Also included

• New config [core] team_name_cache_ttl (default 30s).

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Opus 4.8

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[vincbeck]

CI is failing

[henry3260]

looks good!
test_bulk_delete_query_count_scales_linearly_with_task_count still asserts
the old exact counts, we should update it

[yuseok89]

CI is failing

You're right, sorry. Once it was approved I moved it out of draft, but an approval isn't the same as a green CI, and I should have confirmed that first.

The failure wasn't in the tests this change adds. Caching the Dag team lookup shaves one query off the bulk task-instance delete path, which tripped a pre-existing query-count regression guard there. That's the cross-area interaction I didn't catch. It's now fixed and pushed.

[yuseok89]

closes: #61485

requires_access_dag resolves a Dag's owning team via DagModel.get_team_name on every call — twice per grid endpoint (TASK_INSTANCE + RUN) and on every auto-refresh poll.

This caches the lookup with a short per-process TTL.

Other large costs discussed in #61485 have already been addressed by separate PRs. I left the detailed breakdown in the issue comment, and this PR covers the remaining redundant Dag team lookup.

Impact

Team-ownership DB queries per grid page load:

	first load	follow-up poll
before	6	6
after	1	0

Also included

• New config [core] team_name_cache_ttl (default 30s).

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  • Opus 4.8

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[vincbeck]

CI is failing

[henry3260]

looks good!
test_bulk_delete_query_count_scales_linearly_with_task_count still asserts
the old exact counts, we should update it

[yuseok89]

CI is failing

You're right, sorry. Once it was approved I moved it out of draft, but an approval isn't the same as a green CI, and I should have confirmed that first.

The failure wasn't in the tests this change adds. Caching the Dag team lookup shaves one query off the bulk task-instance delete path, which tripped a pre-existing query-count regression guard there. That's the cross-area interaction I didn't catch. It's now fixed and pushed.