what s the distinction between `cloud workspace yaml` and `l

Question

what s the distinction between `cloud workspace yaml` and `locations yaml` We currently use `locations yaml` for main deployment and `cloud workspace yaml` for branch deployment Is there anyway we can just use the same file It seems pretty redundant What s the best practice

prha · Answer

Hi Frank Both of these are configuration files specifically used by GH actions to automatically add code locations to your various deployments on commits PRs

prha · Answer

The `locations yaml` is used from an older version of the GH action to deploy solely to your prod deployment

prha · Answer

`cloud workspace yaml` is used in the more recent GH integrations for both prod and branch deployments

Sterling Paramore · Answer

I ve been wondering what this file did too I tried using `dagster cloud workspace sync` but just got a bunch of errors I didn t understand So `cloud workspace yaml` is only used by Github actions If I m not using GH I don t need this file

prha · Answer

That s right It s used to map code from your GH repo to a named code location in your deployment

prha · Answer

< Frank Lu> For hybrid deployments we recommend using the GH action pattern that s outlined here

prha · Answer

That being said we have no immediate plans of deprecating support of the old GH action which parses a `location yaml` file

prha · Answer

Apologies it s even more confusing The newest configuration file is named `dagster cloud yaml` It should have the same structure as `cloud workspace yaml` just renamed

prha · Answer

I think `cloud workspace yaml` was only used with beta partners testing out branch deployments

Frank Lu · Answer

awesome i ll consolidate my template to start using `dagster cloud yaml` and remove `locations yaml`