Add --configuration flag to gke-gcloud-auth-plugin

[LogicalShark]

#1056

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

This issue is currently awaiting triage.

If the repository mantainers determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LogicalShark

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• cmd/gke-gcloud-auth-plugin/OWNERS [LogicalShark]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[LogicalShark]

/test all

[LogicalShark]

/assign hdp617

[hdp617]

It's unclear to me how adding the --configuration flag will allow changing the plugin cache location. Could you provide a bit more detail in the description?

[LogicalShark]

Converting back to WiP while looking at potentially passing more gcloud arguments through to the plugin #1056