guan404ming opened a new issue, #62125:
URL: https://github.com/apache/airflow/issues/62125
### Body
Currently, the `materialize_asset` API route (`POST
/assets/{asset_id}/materialize`) creates a `DagRunType.MANUAL` dag run. This
means asset materializations are treated as manual runs and are subject to the
same `allowed_run_types` check.
This may not be the right semantic fit. A dag author might want to deny
manual triggers but still allow materializations (or vice versa).
We should consider adding a dedicated `DagRunType.ASSET_MATERIALIZATION` so
that:
- Authors can independently control whether their DAG accepts
materialization runs vs. manual triggers via `allowed_run_types`.
- Materialization runs are distinguishable from manual runs in the UI, logs,
and audit trail.
Related PR discussion:
https://github.com/apache/airflow/pull/61833#discussion_r2812911121
Parent issue: https://github.com/apache/airflow/issues/61710
### Committer
- [x] I acknowledge that I am a maintainer/committer of the Apache Airflow
project.
--
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]
