Feature Request: Allow passing custom plugin location from CLI parameter

[rawc0der]

Hello everyone,

I am having a hard time using different kustomize versions in my local kubernetes cluster setup (for sanity), made of ArgoCD that is reading sops encrypted files.
I suppose Argo is decently keeping up with the latest Kustomize developments (see argoproj/argo-cd#5967) , but here's where I think a couple of strange behaviours occur.

ArgoCD folklore is managing to integrate the various kustomize releases with the kustomize.path and kustomize.buildOptions options in the configmap/argocd-cm, but default plugin path is only visible to the default kustomize bin.. :(

Would there be any other option than exporting XDG_CONFIG_HOME variable to the environment for setting custom plugin paths?
If the kustomize CLI can have a parameter for setting plugins path, let's say --plugin-path for sake of simplicity, then using kustomize tool v4.0.5 in ArgoCD with something like the following, would be a breeze :).

kustomize.path.v4.0.5: /usr/local/bin/kustomize_4_0_5
kustomize.buildOptions.v4.0.5: "--plugins-path=/.config"

Any thoughts? Thanks.
/cc @chetan-rns @wtam2018

[rawc0der]

In case you are wondering, I found the source of the problem here:

rpc error: code = Unknown desc = `/usr/local/bin/kustomize_4_0_5 build /tmp/https:__code.REDACTED.com/gitops/istio` failed exit status 1: Error: loading generator plugins: external plugins disabled; unable to load external plugin 'ksops'

Please correct me if I'm wrong, thanks again...