potiuk opened a new pull request, #76234:
URL: https://github.com/apache/airflow/pull/76234
`serialize_asset_events` returned every Dag run an asset event triggered,
including runs of Dags the requesting user cannot read. The asset events list
(`GET /assets/events`) and a Dag run's upstream asset events (`GET
/dags/{dag_id}/dagRuns/{dag_run_id}/upstreamAssetEvents`) filtered which events
came back, but not the `created_dagruns` nested in each one. Those are now
narrowed to the user's readable Dags, the same way
https://github.com/apache/airflow/pull/74836 narrowed the Dag and task
references of assets. Both routes reuse the readable Dag ids their event filter
already resolves, so no query is added.
`readable_dag_ids` has no default, so a new caller has to decide whether to
narrow the runs instead of returning all of them by omission.
Related: airflow-s/airflow-s#683
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Opus 5
--
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]
