Hi all, I am very new to Dagster and exploring it for our use-case. Currently going through the docs and got confused between composite solids vs pipelines. We have different sets of computations, each independent, doing the same steps but on different assets (tables) and have different upstream dependencies. I was tempted to create configurable/reusable composite solid, programmatically create new invocations of the composite solid for each set of computations with different config params. But in this case, we cannot execute each set independently as solids are not executable and we might need this capability as each have different upstream dependencies. On the other hand, if I model each set as an independent pipelines, I am not sure how to create them programmatically as pipelines does not support configs. Could someone help me design our use-case and correct me if I am missing something?
I also see there is an ongoing effort to merge pipelines and composite solid into graphs and make solids executable.
https://github.com/dagster-io/dagster/discussions/2902