kubectl config get-contexts: sort output

[kellycampbell]

This sorts the output of kubectl config get-contexts because the ordering is otherwise non-stable and makes it harder to find the context you're looking for when you have more than a few.

The output of kubectl config get-contexts is now sorted alphabetically by the context name.

[k8s-ci-robot]

Hi @kellycampbell. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with @k8s-bot ok to test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[cblecker]

@k8s-bot ok to test

[pwittrock]

/assign alexandercampbell

[pwittrock]

/unassign

[alexandercampbell]

/assign

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please email the CNCF helpdesk: helpdesk@rt.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[kellycampbell]

/test pull-kubernetes-bazel
/test pull-kubernetes-e2e-gce-etcd3

[alexandercampbell]

/retest
/lgtm

[alexandercampbell]

/test pull-kubernetes-bazel

[alexandercampbell]

Seems like a lot of tests are having trouble recently.

I pulled your branch locally to see if there was an issue with an out-of-date bazel file but everything seemed to be updated correctly. Hopefully retesting one more time fixes the issue.

[kellycampbell]

Thanks. I was only able to test the local bazel tests, e.g. bazel test pkg/kubectl:all, as I'm not setup for the e2e tests.

…

On Tue, Aug 1, 2017 at 4:43 PM, Alexander Campbell ***@***.*** > wrote: Seems like a lot of tests are having trouble recently. I pulled your branch locally to see if there was an issue with an out-of-date bazel file but everything seemed to be updated correctly. Hopefully retesting one more time fixes the issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#46946 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAmNTvRRCjv_SCEen2dM9Z1c7om9-kzTks5sT44IgaJpZM4Nvg83> .

[alexandercampbell]

/retest

[cblecker]

/retest

[cblecker]

/retest

[cblecker]

/assign @liggitt
for approval

[nikhiljindal]

This will be so much better, especially for people building automated scripts using kubectl config get-contexts.
Thanks for working on this!

[cblecker]

cc: @kubernetes/kubectl-maintainers

[apelisse]

This should be in for a while.

@pwittrock Can you please approve?
/retest

[shiywang]

/test pull-kubernetes-e2e-gce-etcd3

[cblecker]

Ping @liggitt for approval.
Note that pull-kubernetes-e2e-gce-etcd3 does not exist anymore, but the failure isn't blocking.

[liggitt]

/approve no-issue

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexandercampbell, kellycampbell, liggitt

Associated issue requirement bypassed by: liggitt

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

• pkg/kubectl/OWNERS [liggitt]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[k8s-github-robot]

/test all [submit-queue is verifying that this PR is safe to merge]

[k8s-ci-robot]

@kellycampbell: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-kubernetes-e2e-gce-etcd3	9f74685	link	/test pull-kubernetes-e2e-gce-etcd3
pull-kubernetes-bazel-test	9f74685	link	/test pull-kubernetes-bazel-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 46946, 45792). If you want to cherry-pick this change to another branch, please follow the instructions here.