search

fauna / fauna-shell

Interactive shell for FaunaDB
Other
76 stars 16 forks source link

schema commands require project even when secret option provided #413

Open ptpaterson opened 12 hours ago

ptpaterson commented 12 hours ago

The --secret option effectively escapes out of most project configuration options, but schema command initialization always requires a project.

https://github.com/fauna/fauna-shell/blob/1c5153c5d49076e0501a51c4b9ea0d2f5c2b8ecb/src/lib/schema-command.ts#L33-L57

When --secret is used with schema commit, and schema abandon commands, we should not require a project configuration.

Workarounds in the meantime

You can, of course, create a dummy project, but that's a lot of work.

you can add a dummy directory `--dir .' for example:

fauna schema abandon --secret xxxxxxxx --dir .
fabiotheo commented 3 hours ago

Thanks for opening this issue, @ptpaterson. I ran into the same problem when trying to commit a schema using a database key. Your workaround of specifying --dir . worked perfectly for me:

bash Copiar código fauna schema commit --secret=xxxxxx --dir . I appreciate the detailed explanation and the quick fix. This was a great help, and it saved me from having to create a dummy project just for this task. Hopefully, this requirement can be adjusted in a future release to make the CLI even more user-friendly.

Thanks again!