I would like to set up the

dagster-cloud

CLI in a scripted environment. I tried calling

dagster-cloud config setup --organization myorg --user-token user:abcxyz

but it still prompts interactively for my settings which, in a headless environment, doesn't work. What I want to do is follow up with a code-location update, and that's easier to accomplish with the CLI than the GraphQL API / Python API client. Is there a way to configure it non-interactively? Looking at the branch deployment docs, maybe the answer is to skip config setup entirely and just pass org/deployment/token in the code location update command? Edit: Found the

DAGSTER_CLOUD_API_TOKEN

and

DAGSTER_CLOUD_ORGANIZATION

env vars, confirmed the code location update won't prompt if those values are passed via flag or env var.

Hey @Mark Fickett - mind reposting to the #dagster-cloud channel if you still need help here?

All set but thanks for checking in!