K8s/Helm Question: Deploying via Helm, Dagster Dag Code has to be included as a repository , but this Airbyte/Dagster example doesn’t include a repository (just individual ops/jobs). Again, this might be my ignorance so far in Dagster fundamentals, but curious how to deploy DAG code that isn’t included in a “repo”.

The example you pointed out runs

dagit -f airbyte_demo/slack_github_analytics.py

-f

is an alias for

--python-file

, which tells Dagit to discover a relevant Dagster code objects in a targeted file. However, in the backend, it still goes through a repository, we just create one on the fly. If you take a look at the image on the bottom left, the repository is named

__repository__slack_github_analytics

Thanks @rex, that’s good info. Appreciate the support, and apologies for any future questions as I learn more about Dagster!