Channels
dagster-de
topic-async-execution
dagster-jp
dagster-cube
gigs-freelance
dagster-wandb
dagster-feedback
dagster-machine-learning
dagster-bigquery
dagster-support
dagster-dask
dagster-snowflake
dagster-releases
dagster-dbt
faq-read-me-before-posting
tools
dagster-pipes
project-flexible-range-backfills
data-platform-design
events
dagster-serverless
dagster-noteable
introductions
dagster-airflow
dagster-cloud
random
dagster-airbyte
dagster-spatial
announcements
github-discussions
豆瓣酱帮
dagstereo
dagster-ecs
dagster-kubernetes
jobs
dagster-showcase
data-quality-asset-checks
Powered by
#random
Title
d
Daniel Kim
02/18/2022, 6:41 PM
@won
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
so that we can organize or group jobs and establish multi-tenancy Configuring ops:
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
Configured API:
https://docs.dagster.io/concepts/configuration/configured
Post