Accesso alla console Google Cloud e a Cloud Shell recensioni
178785 recensioni
Mayuri P. · Recensione inserita circa un anno fa
naa
Satheesh Kumar Reddy M. · Recensione inserita circa un anno fa
GANDHODI P. · Recensione inserita circa un anno fa
Ahmed M. · Recensione inserita circa un anno fa
Darpal D. · Recensione inserita circa un anno fa
Mitali p. · Recensione inserita circa un anno fa
There were one or two steps where the names didn't match up exactly, like the MY_REGION="REGION" should be changed to MY_REGION=[REGION] (or if not, specify why it works / is needed), and reexamine the ask to look for "Availability policies" as I could not find anything by that name.
Joshua O. · Recensione inserita circa un anno fa
Ahmed M. · Recensione inserita circa un anno fa
Rodrigo E. · Recensione inserita circa un anno fa
端 李. · Recensione inserita circa un anno fa
Naman P. · Recensione inserita circa un anno fa
Seth M. · Recensione inserita circa un anno fa
Bharath K. · Recensione inserita circa un anno fa
Vishal S. · Recensione inserita circa un anno fa
claude M. · Recensione inserita circa un anno fa
Hetal P. · Recensione inserita circa un anno fa
dan B. · Recensione inserita circa un anno fa
Not enough time for the lab. Are we supposed to rush through the lab, not explore anything, and not having any issue? In Explore the VM details section: Step 5 (cancel) should be before step 4 (Scroll down to the Management section and examine Availability policies.) as the Availability policies are not shown in edit mode On my first time doing the lab, when performing command: gsutil acl get gs://$MY_BUCKET_NAME_1/cat.jpg > acl.txt, I encountered the error: BadRequestException: 400 Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access This preventing me from finishing the lab as time was running close to the end. On my second time doing the lab, I saw that I had previously missed a step to change the bucket-level access on creation. This time I was able to finish the lab properly, but even though I could go quickly through the steps (as I had already explored on my first attempt), I only finished with a few minutes to spare. Therefore I conclude that 1 hour is not enough to finish this lab that is supposed to be about exploring the platform.
Marine T. · Recensione inserita circa un anno fa
Jorge P. · Recensione inserita circa un anno fa
Bucket2 Task did not function student_03_241b7bcb68d9@cloudshell:~ (qwiklabs-gcp-01-7cb078f60b5f)$ gcloud storage buckets create gs://$MY_BUCKET_NAME_2 --location=us-central1 Creating gs://BucketBucket/... ERROR: (gcloud.storage.buckets.create) HTTPError 400: Invalid bucket name: 'BucketBucket'
Greg L. · Recensione inserita circa un anno fa
Tony H. · Recensione inserita circa un anno fa
RAMACHANDRAN G. · Recensione inserita circa un anno fa
Not enough time for the lab. Are we supposed to rush through the lab, not explore anything, and not having any issue? In Explore the VM details section: Step 5 (cancel) should be before step 4 (Scroll down to the Management section and examine Availability policies.) as the Availability policies are not shown in edit mode In a later section, (when performing command: gsutil acl get gs://$MY_BUCKET_NAME_1/cat.jpg > acl.txt) I encountered the error: BadRequestException: 400 Cannot get legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access
Marine T. · Recensione inserita circa un anno fa
Avanish G. · Recensione inserita circa un anno fa
Igor P. · Recensione inserita circa un anno fa
Non garantiamo che le recensioni pubblicate provengano da consumatori che hanno acquistato o utilizzato i prodotti. Le recensioni non sono verificate da Google.