Build a Serverless App with Cloud Run that Creates PDF Files Reviews

Peter I. · Reviewed בערך חודש אחד ago

Jeyson G. · Reviewed בערך חודש אחד ago

Yousif A. · Reviewed בערך חודש אחד ago

Jesus Humberto A. · Reviewed בערך חודש אחד ago

André M. · Reviewed בערך חודש אחד ago

Pier Luigi B. · Reviewed בערך חודש אחד ago

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

Indhu P. · Reviewed בערך חודש אחד ago

Vaibhav T. · Reviewed בערך חודש אחד ago

Nitesh R. · Reviewed בערך חודש אחד ago

Xiao Qing K. · Reviewed בערך חודש אחד ago

Revi G. · Reviewed בערך חודש אחד ago

Priyanka S. · Reviewed בערך חודש אחד ago

rajkumar n. · Reviewed בערך חודש אחד ago

Anton T. · Reviewed בערך חודש אחד ago

nice

Sergio M. · Reviewed בערך חודש אחד ago

Juan pablo A. · Reviewed בערך חודש אחד ago

Nidhi S. · Reviewed בערך חודש אחד ago

muy poco timepo

Juan pablo A. · Reviewed בערך חודש אחד ago

Nidhi S. · Reviewed בערך חודש אחד ago

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

Neptali D. · Reviewed בערך חודש אחד ago

Satin M. · Reviewed בערך חודש אחד ago

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. · Reviewed בערך חודש אחד ago

Felipe S. · Reviewed בערך חודש אחד ago

Christopher K. · Reviewed בערך חודש אחד ago

Roger R. · Reviewed בערך חודש אחד ago