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

dagster

Hi Dagster community, does Dagster currently support graph definitions comprised of operation definitions loaded from different user-deployment/code-locations?

you can reuse op definitions in different graph definitions that are in separate code locations

Thanks, Yuhan! To clarify, if I have op definition A in code location A and op definition B in code location B,  and each code location is hosted in its own code location server, I'll be able to construct a graph definition that executes A, then B?

Atm, Definitions and Repositories don't appear to allow passing operation definitions in user code locations hosted via grpc: <https://docs.dagster.io/_apidocs/definitions#dagster.Definitions>

Is there another way to pass operation definitions to allow the creation of graphs/jobs that refer to ops cross code locations?