You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, FPS "captures" CLI arguments and treats them only as configuration options. Anything else passed to the CLI fails, such as subcommands, or arguments and options that are not configuration-related.
For instance, in quetz run test_quetz --copy-conf ./dev_config.toml --dev --reload:
run is a subcommand.
test_quetz is a required argument.
--copy-conf is an option that has value ./dev_config.toml.
--dev and --reload are flags.
Proposed Solution
FPS should "forward" any subcommand, argument and options that are not configuration-related to the underlying application.
I would probably have a different approach here by "just" defining another CLI using typer.
Why not reusing the same approach as what's done in Quetz CLI?
Problem
Currently, FPS "captures" CLI arguments and treats them only as configuration options. Anything else passed to the CLI fails, such as subcommands, or arguments and options that are not configuration-related.
For instance, in
quetz run test_quetz --copy-conf ./dev_config.toml --dev --reload
:run
is a subcommand.test_quetz
is a required argument.--copy-conf
is an option that has value./dev_config.toml
.--dev
and--reload
are flags.Proposed Solution
FPS should "forward" any subcommand, argument and options that are not configuration-related to the underlying application.
Additional context
This is needed if we want to use FPS in Quetz.
The text was updated successfully, but these errors were encountered: