asdf-gcloud icon indicating copy to clipboard operation
asdf-gcloud copied to clipboard

gcloud warns about other instances on your system PATH

Open jthegedus opened this issue 4 years ago • 1 comments

Describe the bug

gcloud warns about other instances on your system PATH. Is there a way to avoid (or worst case, suppress) this warning?

Steps to reproduce

  1. have a version installed via asdf-gcloud
  2. install another version via asdf-gcloud

Expected behavior

No Warning about other versions to be shown.

Screenshots

✅  gcloud 299.0.0 installed!
ℹ️  Installing SDK Components from /home/jthegedus/.default-cloud-sdk-components


Your current Cloud SDK version is: 299.0.0
Installing components from version: 299.0.0

┌─────────────────────────────────────────────────────────┐
│           These components will be installed.           │
├──────────────────────────────────┬────────────┬─────────┤
│               Name               │  Version   │   Size  │
├──────────────────────────────────┼────────────┼─────────┤
│ Google Cloud Build Local Builder │      0.5.0 │ 6.0 MiB │
│ Google Cloud Build Local Builder │            │         │
│ gcloud Alpha Commands            │ 2019.05.17 │ < 1 MiB │
│ gcloud Beta Commands             │ 2019.05.17 │ < 1 MiB │
└──────────────────────────────────┴────────────┴─────────┘

For the latest full release notes, please visit:
  https://cloud.google.com/sdk/release_notes

╔════════════════════════════════════════════════════════════╗
╠═ Creating update staging area                             ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Installing: Google Cloud Build Local Builder             ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Installing: Google Cloud Build Local Builder             ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Installing: gcloud Alpha Commands                        ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Installing: gcloud Beta Commands                         ═╣
╠════════════════════════════════════════════════════════════╣
╠═ Creating backup and activating new installation          ═╣
╚════════════════════════════════════════════════════════════╝

Performing post processing steps...done.                                                                                                                                                                               

Update done!

WARNING:   There are other instances of Google Cloud Platform tools on your system PATH.
  Please remove the following to avoid confusion or accidental invocation:

  /home/jthegedus/.asdf/shims/java_dev_appserver.sh
/home/jthegedus/.asdf/shims/git-credential-gcloud.sh
/home/jthegedus/.cache/cloud-code/installer/google-cloud-sdk/bin/anthoscli
/home/jthegedus/.cache/cloud-code/installer/google-cloud-sdk/bin/docker-credential-gcloud
/home/jthegedus/.asdf/shims/gcloud
/home/jthegedus/.cache/cloud-code/installer/google-cloud-sdk/bin/dev_appserver.py
/home/jthegedus/.asdf/shims/dev_appserver.py
/home/jthegedus/.asdf/shims/gsutil
/home/jthegedus/.asdf/shims/endpointscfg.py
/home/jthegedus/.cache/cloud-code/installer/google-cloud-sdk/bin/bq
/home/jthegedus/.asdf/shims/cloud-build-local
/home/jthegedus/.asdf/shims/anthoscli
/home/jthegedus/.cache/cloud-code/installer/google-cloud-sdk/bin/gsutil
/home/jthegedus/.cache/cloud-code/installer/google-cloud-sdk/bin/gcloud
/home/jthegedus/.cache/cloud-code/installer/google-cloud-sdk/bin/java_dev_appserver.sh
/home/jthegedus/.asdf/shims/docker-credential-gcloud
/home/jthegedus/.cache/cloud-code/installer/google-cloud-sdk/bin/endpointscfg.py
/home/jthegedus/.cache/cloud-code/installer/google-cloud-sdk/bin/git-credential-gcloud.sh
/home/jthegedus/.asdf/shims/bq

  
✅  Cloud SDK Components installed

Additional context

jthegedus avatar Jul 06 '20 08:07 jthegedus

Is this even an issue? gcloud will complain even though this is just recognizing the existing shim. Perhaps we log to ignore the warning? gcloud warnings can probably be suppressed on installation, though that might hide important warnings. Is a closed, but pinned GitHub Issue describing this warning and that it is fine sufficient, or should we log something?

jthegedus avatar Jul 06 '20 10:07 jthegedus