Add REST API endpoint to materialize asset

[uranusjr]

This is done by triggering the DAG that has the given asset as a task outlet. 409 is returned if more than one DAG uses the asset as outlet.

Close #42318.

[pierrejeambrun]

Code looks good.

To what extend do we really need that endpoint ? While we can just query the asset details (get_asset), check the producing_tasks dag_ids and manually trigger one of those Run via the POST DagRun API if we only have 1 dag affected.

This operates across DagRun, Assets resources and return a 'DagRun' while we are querying the asset resource. All that seems a little confusing to me.

Does it have to be part of the public API ? Or can this be private if really required ?

[bbovenzi]

Yeah, why is this needed? We can already manually trigger a dag run or manually create an asset event through the API.

[uranusjr]

It’s in the vision of the data awareness proposal. The motivation is to be able to treat assets as the central concept like DAGs. When you want an asset to be refreshed, you can operate on the asset directly, instead of needing to go through the thought process of finding what DAG contains a task that refreshes the asset, and triggers that DAG instead (DAG is the central concept in this thought process).

Yeah we definitely don’t really need this, and we probably don’t need to do anything in the UI for 3.0. This is just a new thing that promotes the asset centric idea.

[pierrejeambrun]

Thanks for the details.