Opinie (Clean Up Unused and Orphaned Persistent Disks)

Emil E. · Sprawdzono ponad 6 lat temu

Dhanu S. · Sprawdzono ponad 6 lat temu

Awesome!

Roman M. · Sprawdzono ponad 6 lat temu

Hisato K. · Sprawdzono ponad 6 lat temu

Narayan S. · Sprawdzono ponad 6 lat temu

test

Andre R. · Sprawdzono ponad 6 lat temu

Muhammad Raditya P. · Sprawdzono ponad 6 lat temu

Darryl D. · Sprawdzono ponad 6 lat temu

Kavya K. · Sprawdzono ponad 6 lat temu

Shern Shern Y. · Sprawdzono ponad 6 lat temu

Matthew E. · Sprawdzono ponad 6 lat temu

Thiago B. · Sprawdzono ponad 6 lat temu

Bervianto Leo P. · Sprawdzono ponad 6 lat temu

Isar N. · Sprawdzono ponad 6 lat temu

Paulo C. · Sprawdzono ponad 6 lat temu

Aswani Dutt V. · Sprawdzono ponad 6 lat temu

j n. · Sprawdzono ponad 6 lat temu

Theo G. · Sprawdzono ponad 6 lat temu

Shell disconnected and caused main.py not to be found

Theo G. · Sprawdzono ponad 6 lat temu

José C. · Sprawdzono ponad 6 lat temu

Srikanth P. · Sprawdzono ponad 6 lat temu

Patricia N. · Sprawdzono ponad 6 lat temu

MohammadAshraf V. · Sprawdzono ponad 6 lat temu

Omar M. · Sprawdzono ponad 6 lat temu

When I try to deploy the scheduler, I get the error: "NOT_FOUND: The project qwiklabs-gcp-02-02089e1e60d3 does not contain an App Engine application." I changed to the parent directory (gcf-automated-resource-cleanup) and reran the command to deploy the scheduler and it seems to have worked. (I'm not sure if I just needed to rerun the command or if changing directories actually mattered.) But when I try to test the scheduled run, it fails. I _think_ this is all because of entering the default "N" when asked if the cloud function should allow unauthenticated invocations. In "Output the section of the code that checks the lastAttachTimestamp field and deletes the disk if it doesn’t exist:" the current code in the repo is vastly different from the code shown. There are similar problems for "Output the section of the code that calculates the age of the disk if it’s orphaned, creates a snapshot of it, and deletes it:" Most of these seem related to new try blocks and using [] instead of .get(). "The following diagram describes the architecture used in the first section of this lab, where you schedule a Cloud Function": the Cloud Function isn't scheduled until the last section of the lab (not the first). And the diagram could sure use some text describing the pieces. Sure, it's obvious to you since you've already done the lab but for those just starting the lab, it's not so clear. In Enable APIs and Clone Repository, thank you, thank you, thank you for using environment variables. In examining the created disks, it would be nice if the table could be formatted to fit without wrapping. In "Review the Cloud Function code", I was confused by step 4: "In Cloud Shell, click the Cloud Shell Editor button to edit the main.py file." since I didn't read ahead to step 5 which told me how to navigate to main.py. I figured out where main.py was and then was confused by steps 5 and 6, since I'd already opened main.py to edit. I think I'd have been much less confused if step 4 had just been: "In Cloud Shell, click the Cloud Shell Editor button." When deploying the function, there is a new prompt that needs to be replied to (Allow unauthenticated invocations of new function"). In "Schedule and test the Cloud Function," make it clear you won't actually use the schedule. In looking at my score on the right side, I could only see the first 5 items and couldn't figure out how to get to the 6th.

Laurie W. · Sprawdzono ponad 6 lat temu