Membangun Aplikasi Serverless dengan Cloud Run yang Membuat File PDF Ulasan

Juan Diego N. · Diulas sekitar 1 bulan lalu

Ian S. · Diulas sekitar 1 bulan lalu

Done

Anil B. · Diulas sekitar 1 bulan lalu

Peter I. · Diulas sekitar 1 bulan lalu

Jeyson G. · Diulas sekitar 1 bulan lalu

Yousif A. · Diulas sekitar 1 bulan lalu

Jesus Humberto A. · Diulas sekitar 1 bulan lalu

André M. · Diulas sekitar 1 bulan lalu

Pier Luigi B. · Diulas sekitar 1 bulan lalu

No clean steps . a step in I AM binding to service account. Service account name is given wrong

Indhu P. · Diulas sekitar 1 bulan lalu

Vaibhav T. · Diulas sekitar 1 bulan lalu

Nitesh R. · Diulas sekitar 1 bulan lalu

Xiao Qing K. · Diulas sekitar 1 bulan lalu

Revi G. · Diulas sekitar 1 bulan lalu

Priyanka S. · Diulas sekitar 1 bulan lalu

rajkumar n. · Diulas sekitar 1 bulan lalu

Anton T. · Diulas sekitar 1 bulan lalu

nice

Sergio M. · Diulas sekitar 1 bulan lalu

Juan pablo A. · Diulas sekitar 1 bulan lalu

Nidhi S. · Diulas sekitar 1 bulan lalu

muy poco timepo

Juan pablo A. · Diulas sekitar 1 bulan lalu

Nidhi S. · Diulas sekitar 1 bulan lalu

Dockerfile seems is not properly updated to run when deploying in cloud run.

Neptali D. · Diulas sekitar 1 bulan lalu

Satin M. · Diulas sekitar 1 bulan lalu

Overall Feedback: Great lab on event-driven architecture with Cloud Run and Pub/Sub, but there are two significant IAM/service account blockers in Task 4 that prevent users from completing the steps as written. Issue 1: Missing permission for Cloud Storage to publish to Pub/Sub Description: When running the gsutil notification create command, it fails with a BadRequestException: 400 because the Cloud Storage service account lacks permission to publish to the newly created new-doc topic. Suggested Fix: Please update the instructions to explicitly grant the roles/pubsub.publisher role to the Storage Service Agent before creating the notification. Code fix: Bash GCS_SA=$(gcloud storage service-agent) gcloud pubsub topics add-iam-policy-binding new-doc \ --member="serviceAccount:$GCS_SA" \ --role="roles/pubsub.publisher" Issue 2: Pub/Sub Service Agent does not exist when applying IAM permissions Description: When attempting to grant the iam.serviceAccountTokenCreator role to the Pub/Sub service account (service-[PROJECT_NUMBER]@gcp-sa-pubsub.iam.gserviceaccount.com), the command fails with INVALID_ARGUMENT: Service account... does not exist. Enabling the Pub/Sub API does not provision this identity fast enough (or at all) in the lab environment. Suggested Fix: Please add a command to explicitly force the creation of the Pub/Sub service identity prior to the IAM binding step. Code fix: Bash gcloud beta services identity create --service=pubsub.googleapis.com --project=$GOOGLE_CLOUD_PROJECT Minor Note on Deprecation: The lab still relies heavily on gsutil mb and gsutil notification create, which throws multiple console warnings recommending the newer gcloud storage CLI. Updating these to gcloud storage buckets create would make the output cleaner for students.

Sangeeth P. · Diulas sekitar 1 bulan lalu