Build a Serverless App with Cloud Run that Creates PDF Files Reviews
49295 reviews
Juan Diego N. · Reviewed 3 месяцев ago
Ian S. · Reviewed 3 месяцев ago
Done
Anil B. · Reviewed 3 месяцев ago
Peter I. · Reviewed 3 месяцев ago
Jeyson G. · Reviewed 3 месяцев ago
Yousif A. · Reviewed 3 месяцев ago
Jesus Humberto A. · Reviewed 3 месяцев ago
André M. · Reviewed 3 месяцев ago
Pier Luigi B. · Reviewed 3 месяцев ago
No clean steps . a step in I AM binding to service account. Service account name is given wrong
Indhu P. · Reviewed 3 месяцев ago
Vaibhav T. · Reviewed 3 месяцев ago
Nitesh R. · Reviewed 3 месяцев ago
Xiao Qing K. · Reviewed 3 месяцев ago
Revi G. · Reviewed 3 месяцев ago
Priyanka S. · Reviewed 3 месяцев ago
rajkumar n. · Reviewed 3 месяцев ago
Anton T. · Reviewed 3 месяцев ago
nice
Sergio M. · Reviewed 3 месяцев ago
Juan pablo A. · Reviewed 3 месяцев ago
Nidhi S. · Reviewed 3 месяцев ago
muy poco timepo
Juan pablo A. · Reviewed 3 месяцев ago
Nidhi S. · Reviewed 3 месяцев ago
Dockerfile seems is not properly updated to run when deploying in cloud run.
Neptali D. · Reviewed 3 месяцев ago
Satin M. · Reviewed 3 месяцев 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 3 месяцев ago
We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.