Hi all! Is it possible to specify an

IOManager

for the output of a composite solid? A toy version of my scenario below. I would like to be able to use

func_b

as part of several composite solids, and I don’t know that I always want to use

my_custom_io_manager

with

func_b

. I do know that I always want to use

my_custom_io_manager

with the composite solid

func_b_a

. With the setup below, running

func_b_a_pipeline

does not use

my_custom_io_manager

and uses the default in-memory manager instead. When I move the

OutputDefinition

to the decorator for

func_b

, the custom io manager is used, but this means that I’m always using this io manager whenever I use func_b, which is not desirable for me. I’m new to Dagster, any ideas on workarounds are appreciated.

@solid
def func_a() -> ReturnsSomething:
    ...

@solid
def func_b(input) -> AlsoReturnsSomething:
    ...

@composite_solid(
    output_defs=[OutputDefinition(io_manager_key="key_for_my_custom_io_manager")]
)
def func_b_a():
    return func_b(func_a())

@pipeline
def func_b_a_pipeline():
    func_b_a():

The outputs of composite solids are "mapped" from the underlying solids that produce them, meaning that the io manager specified on the underlying solid is the one that will always be used to persist that output.

@chris Thank you, a user warning would have definitely been helpful!