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

dagster

Why can't we add InputManager to a source_asset? Seems these things should go hand in hand, now I need to create an IO manager that is noop on the output

Assuming the IOManager wouldn’t be used elsewhere in your DAG (as you can use a full IOManager with source assets), you could always create a class with nothing but the no-op output function, then subclass that whenever you need to create an input only IOManager 

Because the assets are residing in a source that requires it's own input, there is no need to add output handle

Just thought it was weird that input manager exists but you cannot use it on the only place that actually made total sense to use it  :slightly_smiling_face:

I’ve never actually come across InputManagers before! The fact they refer to solids in their docstring suggests to me that they are from the old (pre 1.0) API 