Any way to drop dependency on "github.com/google/shlex"?

[dims]

What happened?

https://github.com/google/shlex has been archived since Dec 29, 2022

What's the best way to avoid depending on this repo?

xref: kubernetes/kubernetes#120276

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

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

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.

[justinsb]

I think we removed the direct dep in #5842 ?

go mod why github.com/google/shlex
# github.com/google/shlex
sigs.k8s.io/kustomize/hack
github.com/cli/cli/cmd/gh
github.com/cli/cli/pkg/cmd/alias/expand
github.com/google/shlex

I think the dep comes in via tools.go here (i.e. not a "real" dep that makes it into compiled code):

kustomize/hack/tools.go

Line 38 in 7372f97

_ "github.com/cli/cli/cmd/gh"

Maybe we should update to the new go tools support, though my understanding is that it doesn't really fix the go.mod issue.

[koba1t]

I feel kubernetes/kubernetes#120276 is caused by we haven't make new release after #5847 merged.

/assign

[koba1t]

We released new kustomize.
https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv5.7.0

/close

[k8s-ci-robot]

@koba1t: Closing this issue.

In response to this:

We released new kustomize.
https://github.com/kubernetes-sigs/kustomize/releases/tag/kustomize%2Fv5.7.0

/close

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.