Opinie (Accessing the Google Cloud Console and Cloud Shell)
185558 opinii
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. · Sprawdzono ponad rok temu
Ahmed M. · Sprawdzono ponad rok temu
Rodrigo H. · Sprawdzono ponad rok temu
duan 李. · Sprawdzono ponad rok temu
Naman P. · Sprawdzono ponad rok temu
Seth M. · Sprawdzono ponad rok temu
Bharath K. · Sprawdzono ponad rok temu
Vishal S. · Sprawdzono ponad rok temu
claude M. · Sprawdzono ponad rok temu
Hetal P. · Sprawdzono ponad rok temu
dan B. · Sprawdzono ponad rok temu
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. · Sprawdzono ponad rok temu
Jorge P. · Sprawdzono ponad rok temu
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. · Sprawdzono ponad rok temu
Tony H. · Sprawdzono ponad rok temu
RAMACHANDRAN G. · Sprawdzono ponad rok temu
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. · Sprawdzono ponad rok temu
Avanish G. · Sprawdzono ponad rok temu
Igor P. · Sprawdzono ponad rok temu
Cannelle P. · Sprawdzono ponad rok temu
Son T. · Sprawdzono ponad rok temu
A few steps were slightly incorrect, but I was able to work around the differences.
Bryan V. · Sprawdzono ponad rok temu
Ksenia Z. · Sprawdzono ponad rok temu
Francis C. · Sprawdzono ponad rok temu
the commands are a bit lost, lots of come & go, and there are vm instances that are just there for nothign !
Ayoub H. · Sprawdzono ponad rok temu
Nie gwarantujemy, że publikowane opinie pochodzą od konsumentów, którzy dane produkty kupili lub ich używali. Google nie weryfikuje opinii.