The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

how do i use an IO manager with a graph backed asset? i don’t see anything in the source code or in the docs…

should the graph backed asset not be reliant on an IO manager? what about inter-op io management?

<@U016C4E5CP8> looks like a bug:
<https://github.com/dagster-io/dagster/blob/e425f14f7177fe0147bd626bf245819bdf2fc1a5/python_modules/dagster/dagster/_core/definitions/decorators/asset_decorator.py#L758-L770|https://github.com/dagster-io/dagster/blob/e425f14f7177fe0147bd626bf245819bdf2fc1a[…]dagster/dagster/_core/definitions/decorators/asset_decorator.py>

`resource_defs` isn’t being forwarded anywhere which means you can’t define your own resources for a graph backed asset.

maybe there is a reason why `resource_defs` isn’t included as part of this decorator that i’m not aware of?

<https://docs.dagster.io/_apidocs/assets#dagster.AssetsDefinition.from_graph> `AssetsDefinition.from_graph` supports the `resource_defs` argument so i’d imagine its just an oversight

i’d expect something like this:
```@graph_asset(group_name="MyGroup", resource_defs={"io_manager": my_io_manager})```
to work

would you turn a graph into a job, and apply the io manager to the job? That's what i'm doing at the moment

(or create a job from the graph, I guess)

i’d like to use the asset APIs, but if not possible then yeah that’s what i’ll do

it looks like `@graph_asset` doesn't currently have a `resource_defs` argument. if you file a github issue for this, we can try to get to adding one. we'd also be happy to review a PR if you're interested in contributing.

&gt; how do i use an IO manager with a graph backed asset? i don’t see anything in the source code or in the docs…
the main way to do this is to set an io_manager_key on the op inside the graph

here's an issue where we're tracking making it possible to set an io_manager_key when defining the graph asset: <https://github.com/dagster-io/dagster/issues/9357>

thanks sandy! really appreciate the response. i’ll look to shoot a PR over for that resource_defs update sometime this week!

<https://github.com/dagster-io/dagster/pull/13418> <@U011CET83FG> thanks again :slightly_smiling_face:

<@U011CET83FG> bumping this thread, any updates here? happy to do any extra leg work necessary as this update is blocking a release for my team at work

I somehow missed this - thanks for the reminder. I just kicked off a built to run our test.

just pushed `make black` :slightly_smiling_face:

hmm i see buildkite is still failing - is there anything else i need to do?

<@U011CET83FG> any idea when this update will get released? i don’t see my merge commit as part of the `1.3.1` release tag