关于“Implementing Least Privilege IAM Policy Bindings in Cloud Run [APPRUN]”的评价

Erin C. · 已于 over 3 years前审核

Yoshikawa T. · 已于 over 3 years前审核

Diogo S. · 已于 over 3 years前审核

Lucas G. · 已于 over 3 years前审核

Sonata R. · 已于 over 3 years前审核

Sam H. · 已于 over 3 years前审核

Edoardo F. · 已于 over 3 years前审核

Good

M J. · 已于 over 3 years前审核

lab is incomplete!

Arash A. · 已于 over 3 years前审核

Haru K. · 已于 over 3 years前审核

Giles W. · 已于 over 3 years前审核

Melanie H. · 已于 over 3 years前审核

The lab seems incomplete. Although we did create a dedicated service account for invoking Cloud Run, we did not attach it to a Cloud Scheduler and test the invoking of Cloud Run using Cloud Scheduler which was the requirement as mentioned in the lab.

Shivam A. · 已于 over 3 years前审核

Arun W. · 已于 over 3 years前审核

Victor S. · 已于 over 3 years前审核

Xiang S. · 已于 over 3 years前审核

δυς β. · 已于 over 3 years前审核

Ramkumar E. · 已于 over 3 years前审核

Berenger S. · 已于 over 3 years前审核

Lakmal F. · 已于 over 3 years前审核

Adhi Kesavapillai A. · 已于 over 3 years前审核

Mohammad H. · 已于 over 3 years前审核

1. compared to previous LAB, yet another way to fetch URL is used: previous: URL=$(gcloud run services describe product-service --platform managed --region=us-central1 --format="value(status.address.url)") this one: URL==$(gcloud run services list --format='value(URL)' --filter="quickway") a bit confusing, even though, if you're attentive enough, it helps you understand the basics of gcloud command. Too bad this learning is not explicit. 2. you really should let the student check the newly created service account has permissions on the deployed service. 3. The permission that tickles the so called security team was not clearly identified for me in the LAB. I had to create both unsecure and secure service to check the difference was in Cloud Run Invoker

Serge L. · 已于 over 3 years前审核

Murugan J. · 已于 over 3 years前审核

Gowtham C D. · 已于 over 3 years前审核