19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
Channels
announcements
dagster-airbyte
dagster-airflow
dagster-bigquery
dagster-cloud
dagster-cube
dagster-dask
dagster-dbt
dagster-de
dagster-ecs
dagster-feedback
dagster-kubernetes
dagster-machine-learning
dagster-noteable
dagster-releases
dagster-serverless
dagster-showcase
dagster-snowflake
dagster-spatial
dagster-support
dagster-wandb
dagstereo
data-platform-design
events
faq-read-me-before-posting
gigs-freelance
github-discussions
introductions
jobs
random
tools
豆瓣酱帮
Title
s
Sven Lito
12/14/2022, 5:17 PMLooking to clarify my understanding of branch deploys, Do we need an additional dagster_cloud.yaml or should the prod deploy config be sufficient for this?
d
daniel
12/14/2022, 5:30 PMHey Sven - you shouldn't need a separate dagster_cloud.yaml for branch deployments (but you also shouldn't need to specify an ECR registry when running in serverless - in serverless, we host the image for you)
You can see an example dagster_cloud.yaml for serverless in our quickstart repo: https://github.com/dagster-io/dagster-cloud-serverless-quickstart/blob/main/dagster_cloud.yaml - it doesn't need to specify a registry, unlike hybrid
s
Sven Lito
12/14/2022, 5:35 PMSorry I'm running a hybrid setup.
d
daniel
12/14/2022, 5:35 PMAh, did you possibly change from serverless to hybrid at some point?
s
Sven Lito
12/14/2022, 5:36 PMI have, however the prod deploy is fine. Only branch deploys are giving me trouble
d
daniel
12/14/2022, 5:36 PMGot it - I think this is something we can fix on our side, will report back
🙌 1
OK - as long as you have a hybrid agent set up to serve branch deployments and you're running the hybrid github action, I would expect that error to no longer occur
s
Sven Lito
12/14/2022, 5:46 PMok, let me re-run and report back. Thanks again @daniel
Works now ❤️
😛artydagster: 1