Hey, if I have multiple repos with assets for dagster, say managed by different teams, would I have a

dagster_cloud.yaml

for each of them or should I have one repo with one

dagster_cloud.yaml

used for configs?

We have multiple github repositories, and in that case, you need separate

dagster_cloud.yaml

files to run the separate Github Actions in each. If you have multiple Dagster repositories, but they're all in one code location, or in one Github Repository, I think you can just use one dagster_cloud.yaml.

Great - thanks - do you use separate agents or task definitions for these? Or is it just configuration per job…my use case is for environment variables from secrets manager

Hi Sam, you can use per location configuration for secretsmanager: https://docs.dagster.io/dagster-cloud/deployment/agents/amazon-ecs/configuration-reference#per-location-configuration