bbovenzi opened a new pull request, #47645:
URL: https://github.com/apache/airflow/pull/47645

   For asset triggered dags, add a popover to the Schedule component to see a 
visualization of the asset conditions to trigger the dag.
   - For regularly scheduled dags, the schedule is just text with a tooltip. 
For Asset-triggered dags, it is a button to open a popover
   - Added `asset_expression` to `ui/dags`
   
   
   - To Do: Add event info when we add `asset_id` to `asset_expression`. Right 
now there is no good way to connect an expression to its actual asset. We can 
use this to show the queue for the next dag run, or if a dag run is selected, 
what events caused that dag to trigger. We could also add the Asset Event 
Creation trigger inside this popover.
   
   <img width="399" alt="Screenshot 2025-03-11 at 5 12 25 PM" 
src="https://github.com/user-attachments/assets/bb46c5eb-79a8-46fb-baf0-16f8650c32f0";
 />
   <img width="798" alt="Screenshot 2025-03-11 at 5 12 36 PM" 
src="https://github.com/user-attachments/assets/ed7af4aa-4106-423b-9a40-a1aa80b3e899";
 />
   
   
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   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 
[newsfragments](https://github.com/apache/airflow/tree/main/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]

Reply via email to