Stephen Bailey01/09/2023, 11:33 PM
jordan01/10/2023, 1:44 AM
Stephen Bailey01/10/2023, 1:46 PM
jordan01/10/2023, 4:21 PM
calls once the branch deployment is created. It’s still not entirely clear to me where you’d choose to source the locations from separate github repos from. It feels like a similar challenge to managing PRs when changes live across multiple repos.
dagster-cloud workspace add-location
Stephen Bailey01/10/2023, 4:33 PM
repo, and a separate
repo. It's useful to keep them separate because the Dagster code rarely actually changes in the dbt project, but the project definitions change at an entirely different cadence to the other repositories. If we had branch deployments, users could try running their new models via Dagster (for example).
jordan01/10/2023, 10:57 PM
repo’s CI to also redeploy your
locations after the branch deployment is created.
locations to latest or something similarly stable