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

Yousif A. · Reviewed yaklaşık 1 ay ago

Jesus Humberto A. · Reviewed yaklaşık 1 ay ago

André M. · Reviewed yaklaşık 1 ay ago

Pier Luigi B. · Reviewed yaklaşık 1 ay ago

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

Indhu P. · Reviewed yaklaşık 1 ay ago

Vaibhav T. · Reviewed yaklaşık 1 ay ago

Nitesh R. · Reviewed yaklaşık 1 ay ago

Xiao Qing K. · Reviewed yaklaşık 1 ay ago

Revi G. · Reviewed yaklaşık 1 ay ago

Priyanka S. · Reviewed yaklaşık 1 ay ago

rajkumar n. · Reviewed yaklaşık 1 ay ago

Anton T. · Reviewed yaklaşık 1 ay ago

nice

Sergio M. · Reviewed yaklaşık 1 ay ago

Juan pablo A. · Reviewed yaklaşık 1 ay ago

Nidhi S. · Reviewed yaklaşık 1 ay ago

muy poco timepo

Juan pablo A. · Reviewed yaklaşık 1 ay ago

Nidhi S. · Reviewed yaklaşık 1 ay ago

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

Neptali D. · Reviewed yaklaşık 1 ay ago

Satin M. · Reviewed yaklaşık 1 ay 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 yaklaşık 1 ay ago

Felipe S. · Reviewed yaklaşık 1 ay ago

Christopher K. · Reviewed yaklaşık 1 ay ago

Roger R. · Reviewed yaklaşık 1 ay ago

gopi krishna A. · Reviewed yaklaşık 1 ay ago

there is not enough time to complete these labs

Ramon L. · Reviewed yaklaşık 1 ay ago