imrichardwu opened a new pull request, #62189:
URL: https://github.com/apache/airflow/pull/62189
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
This PR introduces backend and API support for exposing per-DAG-run deadline
information to the UI.
## Changes included
### API and data model
- GridRunsResponse gains a has_missed_deadline: bool field, allowing the
Grid view to surface
deadline status without additional API calls.
### New private UI endpoint
- Adds a private UI router mounted at /ui/deadlines/{dag_id}/{run_id}.
- The endpoint fetches all Deadline rows for the given DAG run, joined with
their associated
DeadlineAlert records.
- Results are ordered by deadline_time and returned as DeadlineResponse
objects.
### New response model
DeadlineResponse includes:
- id
- deadline_time
- missed
- created_at
- alert_name (nullable)
- alert_description (nullable)
### OpenAPI
- Updates _private_ui.yaml to document the new endpoint and response schema.
- Regenerates the TypeScript client accordingly.
## Notes
- No UI rendering logic is included in this PR.
- This PR only exposes the data required by the UI, keeping frontend
concerns separate.
I am in the MLH Fellowship and working with @ferruzzi, so there are no
GitHub issues for this.
---
##### Was generative AI tooling used to co-author this PR?
- [ ] Yes (please specify the tool below)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#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](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
--
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]
