Difference: config pyproject.toml/dagster_cloud.yaml

[dbrtly]

Under what circumstances are these two config intended to be different for a dagster project deployed to dagster cloud? I don't understand why
dagster_cloud.yaml is necessary.

I'm willing to contribute here.

pyproject.toml

[tool.dagster]
module_name = "quickstart_etl.definitions"
code_location_name = "quickstart_etl"

dagster_cloud.yaml

locations:
  - location_name: my_location_name # the name of the code location
    code_source:
      package_name: hackernews # the name of the python package associated with the code location

Motivation: simplify tasks required to deploy to dagster+.

[zyd14]

How do you specify multiple code locations with pyproject.toml? Mostly just curious

[dbrtly]

How do you specify multiple code locations with pyproject.toml? Mostly just curious

I poked around in the oldest dagster docs for explanation of workspace.yaml and module_name/modules. Originally there was an idea to have something like multiple packages in your dagster workspace that had a degree of isolation for testing and execution. Seems to have been deprioritised though. Footprints of the approach still exist in the codebase.

https://github.com/dagster-io/dagster/blob/master/python_modules/dagster/dagster/_core/workspace/load_target.py#L44-L80