Assigned
Status Update
No update yet.
Comments
gr...@gmail.com
Hi, this error only affects Cloud SDK version 186. It was previously reported in
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
wb...@google.com
If you could provide more details about the functionality and how do you expect it to work I can make a feature request to the product team.
p....@gmail.com
I expect that when I specify --verbosity for gcloud command, it will set level of logs in ~/.config/gcloud/logs as well.
I.e.:
gcloud logging read <...> --verbosity=none
Will tell gcloud not to write any logs to ~/.config/gcloud/logs.
Thank you!
I.e.:
gcloud logging read <...> --verbosity=none
Will tell gcloud not to write any logs to ~/.config/gcloud/logs.
Thank you!
wb...@google.com
I've just created a feature request and added your description. There's no ETA for this so be patient and wait. I'm reassigning this issue to a proper team. Thanks for your feedback on this !
p....@gmail.com
Thank you!
Description
What you would like to accomplish:
I'm downloading historical logs using *gcloud logging read* command.
And for example while downloading around 7Gi of logs, gcloud creates more than 20Gi of its own logs in in ~/.config/gcloud/logs
How this might work:
It could be a kind of switch for this command, i.e. --logs=none(warning, info, etc.), which will prevent gcloud from producing these tones of logs which full disk space with useless (for me) information and causing high IOPS load.
If applicable, reasons why alternative solutions are not sufficient:
Setting --verbosity switch to none didn't help.
Other information (workarounds you have tried, documentation consulted, etc):
As a workaround I delete these logs manually during gcloud run.