Configuring IAM Permissions with gcloud Reviews

Nice

Yash K. · Reviewed over 1 year ago

Amit k. · Reviewed over 1 year ago

Nice

Yash K. · Reviewed over 1 year ago

Saurabh W. · Reviewed over 1 year ago

Himanshu S. · Reviewed over 1 year ago

Daksh C. · Reviewed over 1 year ago

Manish Kumar Yadav G. · Reviewed over 1 year ago

MARAM L. · Reviewed over 1 year ago

Oneplus 5. · Reviewed over 1 year ago

Jason L. · Reviewed over 1 year ago

Diego A. · Reviewed over 1 year ago

Harindu O. · Reviewed over 1 year ago

Nandhakumar P. · Reviewed over 1 year ago

Erick h. · Reviewed over 1 year ago

Manish A. · Reviewed over 1 year ago

Daniel D. · Reviewed over 1 year ago

HAKESH K. · Reviewed over 1 year ago

Abdellatif D. · Reviewed over 1 year ago

nno

Govardhana R. · Reviewed over 1 year ago

good

Rupak R. · Reviewed over 1 year ago

Mykyta T. · Reviewed over 1 year ago

tasks can not be completed from the cloud shell, it's not that obvious why. If I try to do them from the cloud shell: task "Update the default zone" can not be verified. the $CLOUDSDK_CONFIG env var is set to /tmp/tmp.jziMeGlQWi So the gcloud config is not being saved to ~/.config/gcloud/configurations/config_default Even if I unset CLOUDSDK_CONFIG env var, so the default config path is used, do the clean "gcloud auth login", set the zone to something-b then to something-a, checking the contents of the ~/.config/gcloud/configurations/config_default is correct and the new zone is saved there -t ask verification failing anyway. I don't know what is actually lab creator is checking in my filesystem or in my environment - so it's impossible to debug. Please improve the labs - do not implement any indirect checks that are impossible to debug.

Yuri G. · Reviewed over 1 year ago

Sornam S. · Reviewed over 1 year ago

Lab

Gaurav K. · Reviewed over 1 year ago

Sumit N. · Reviewed over 1 year ago