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
As means to unblock #1198 + taking inspiration from #1155 and #1207
Since the trigger args in spin up aren't known ahead of time, and actually meant to be forwarded to a spin trigger [...] command, allowing them to be intermixed with spin up args is not conventional. It appears the expected pattern is "cmd [args] -- [next args]"
Compare with cargo run which is analogous:
NAME
cargo-run — Run the current package
SYNOPSIS
cargo run [options] [-- args]
DESCRIPTION
Run a binary or example of the local package.
All the arguments following the two dashes (--) are passed
to the
binary to run. If you’re passing arguments to both Cargo an
d the
binary, the ones after -- go to the binary, the ones before
go to
Cargo.
This avoids any kind of ambiquity with future spin up args and makes parsing easier possible in clap 4.