Non-interactive `convex dev` not working
Is there a way to configure
convex dev
without a prompt? Using convex dev --configure new --project <app-name> --dev-deployment local
still gives a prompt. This is very unexpected since all of the details needed to set up a local Convex instance is already provided, and the --help
docs seem to imply that --configure
is non-interactive when using additional flags ("... interactively or set by ...", emphasis mine).9 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
If you add the --team <team-name> flag it runs non-interactively
This does not work, I still get a prompt asking questions that are already answered by the CLI arguments.
If you have Convex already installed:
no prompts
Created project test-10362, manage it at https://dashboard.convex.dev/t/erquhart/test-10362This seems like you've already logged into Convex, is that a prerequisite just to use local development non-interactively? When I run that exact command, I immediately get the prompt asking me if I want to start without an account or login, even though the CLI should already know the answer based on the options I pass in.
Convex Dashboard
Manage your Convex apps
Ah yeah - if you're not authenticated it can't do anything, so interaction is required.
But once you authenticate once on your system, you're good. Don't have to do it per project.
But it shouldn't require authentication. If I select the local option, it runs fine, but there's no way to set that up non-interactively.
Aaahh I see what you're saying - yeah, it would probably make sense for
--dev-deployment local
to have that effect+ 1, is there any way to bypass inteaction for local deployments
it works fine with cloud deployments if u add the deployment key