https://dagster.io/ logo
#dagster-cloud
Title
# dagster-cloud
a

Aki Iwa

07/23/2023, 1:18 AM
Also, dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v0.1 but is there a better way to selectively deploy only those locations where code changes have occurred?
s

Shalabh Chaturvedi

07/23/2023, 4:00 AM
If you switch to the new CICD workflow here: https://github.com/dagster-io/dagster-cloud-hybrid-quickstart/, you can have more control of which locations get deployed. Note the
ci-init
step can be passed a list of location names that should be deployed: https://github.com/dagster-io/dagster-cloud-hybrid-quickstart/#deploy-a-subset-of-code-locations To deploy only some locations you would implement a
get-locations
step before the
ci-init
step. The
get-locations
should set an output that contains the json list of locations you want to deploy. You can then use that output in the
location_names
input of
ci-init
. To implement
get-locations
you may have to write a script that checks the git log for paths that have changed.
a

Aki Iwa

07/23/2023, 4:09 AM
I still need to switch workflows. There is also the issue of
No module named xxxxx
above, and we may want to switch it. Thank you.