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

dagster

<@U02M6CBFKH6> Have you looked at documentation for workspace.yaml?  Also, I make folders for ops, graphs, and repositories.  Then group jobs from dagster repository abstraction.  Of course, there are many ways to organize your codebase.

I refer to these references constantly and are in my personal dagster "cheat sheet":

Repository and Workspace Abstractions:
<https://docs.dagster.io/concepts/repositories-workspaces/repositories|https://docs.dagster.io/concepts/repositories-workspaces/repositories>
so that we can organize or group jobs and establish multi-tenancy

Configuring ops:
<https://docs.dagster.io/concepts/configuration/config-schema#examples|https://docs.dagster.io/concepts/configuration/config-schema#examples>

Passing same config to multiple ops:
<https://docs.dagster.io/concepts/configuration/config-schema#passing-configuration-to-multiple-ops-in-a-job|https://docs.dagster.io/concepts/configuration/config-schema#passing-configuration-to-multiple-ops-in-a-job>

Configured API:
<https://docs.dagster.io/concepts/configuration/configured|https://docs.dagster.io/concepts/configuration/configured>