Skip to content
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

Convert commands over to use pflag library for POSIX style opts #332

Merged
merged 1 commit into from
Jul 21, 2017

Conversation

berrange
Copy link
Contributor

The standard Go flag library treats long & short options as
identical (eg --foo & -foo are the same). This prevents the
creation of short aliases for flags. The replacement pflag
library supports full POSIX opts syntax where long and
short options are distinct. The virtctl command already
uses this library. Convert the remaining commands over to
use it too, so we can later add short options for common
args.

Signed-off-by: Daniel P. Berrange berrange@redhat.com

Copy link
Member

@stu-gott stu-gott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it occurred to me to check the hack, cluster, and manifests directories to see if we were using this behavior anywhere. We're not calling any scripts using single-flag notation, but at least one script is using this same approach: cluster/vm-isolation-check.sh

@rmohr
Copy link
Member

rmohr commented Jul 21, 2017

needs a rebase. Otherwise fine.

The standard Go flag library treats long & short options as
identical (eg --foo & -foo are the same). This prevents the
creation of short aliases for flags. The replacement pflag
library supports full POSIX opts syntax where long and
short options are distinct.  The virtctl command already
uses this library. Convert the remaining commands over to
use it too, so we can later add short options for common
args.

Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
@berrange
Copy link
Contributor Author

Rebased

@stu-gott stu-gott merged commit 6342a1c into kubevirt:master Jul 21, 2017
kubevirt-bot pushed a commit to kubevirt-bot/kubevirt that referenced this pull request Nov 6, 2020
* add e2e functional test steps

* addressing comments
kubevirt-bot pushed a commit to kubevirt-bot/kubevirt that referenced this pull request Dec 7, 2021
At multi node cluster non master nodes were missing the node-role label at all
, also mono node cluster has only master node-role, all this prevent some testing
that depends on those labels.

Signed-off-by: Quique Llorente <ellorent@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants