-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flag parsing error in non-quoted-field #2574
Comments
@baude PTAL |
Less complicated reproducer, courtesy of @mheon on IRC:
|
do you need to specify --label multiple times, or do you expect people to use it as a CSV. If 'as a CSV' that's what you have and 'true="false"' isn't a valid CSV. If you want people to have to use it multiple times I'm guessing you want a StringArray, instead of a StringSlice. |
We use --label multiple times. |
switch from a stringslice to a stringarray for labels to handle quoted input. fixes issue containers#2574 Signed-off-by: baude <[email protected]>
Fixed in master. |
New: - podman exec - podman load (requires containers#2674) - CLI parsing (regression test for containers#2574) Improved: - help: test "podman NoSuchCommand", and subcommands - help: test "podman cmd" without required args - pod: start with --infra=false; this allows running rootless - log: also run 'logs' after container is run - log: test -f with two containers Also, use helpful descriptions for skip_if_rootless Tested on f29, root and rootless. As soon as podman-remote supports rm, I'll start testing that too. Signed-off-by: Ed Santiago <[email protected]>
Does this fix also need to be applied to --env? Slight modification of your reproduction above:
|
#2717 fixed |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Flag parsing error in non-quoted-field, regression found in 1.1.2.
Steps to reproduce the issue:
Command used to deploy:
Describe the results you received:
Describe the results you expected:
Deployment worked in podman 1.0.0.
Output of
podman version
:Output of
podman info --debug
:The text was updated successfully, but these errors were encountered: