Bug: surreal start --allow-funcs <path> will use <path> as the value for the argument

[liusong1111]

Describe the bug

If I run:

surreal start --allow-funcs file:/db

I want start surreal with file storage allowing all funcs, but surreal starts with memory storage.

Steps to reproduce

Finally I found the root cause.

surreal start -h prints:

 --allow-funcs [<ALLOW_FUNCS>...]  Allow execution of all functions. Optionally, you can provide a comma-separated list of function names to allow [env:
                                        SURREAL_CAPS_ALLOW_FUNC=] [default: ]

It says --allow-funcs accepts zero or one argument. zero argument means allow-all-funcs.

The command line:

surreal start --allow-funcs file:/db

It seems that surreal takes file:/db as argument of --allow-funcs, not the [PATH] part.

The annoying thing is: surreal didn't report any error or warning.

Expected behaviour

I suggest use --allow-all-funcs or --allow-funcs <ALLOW_FUNCS>.

The same as --allow-net, --deny-funcs, --deny-net.

Another approch is change the cli pattern to surreal start [PATH] [OPTIONS], disallow usage of surreal start [OPTIONS] [PATH], and change Documentation everywhere(like https://hub.docker.com/r/surrealdb/surrealdb), and report clear error message if possible.

SurrealDB version

v1.4.2

Contact Details

No response

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct

[liusong1111]

btw, run in docker with user 65532 should be treated as a bug, otherwise it will frustrate new users:

#3468
surrealdb/docs.surrealdb.com#315