Cloud Run を使用して PDF ファイルを作成するサーバーレス アプリをビルドする のレビュー

Alarfaj Yousif · 約1ヶ月前にレビュー済み

Angulo Hernandez Jesus Humberto · 約1ヶ月前にレビュー済み

Mota André · 約1ヶ月前にレビュー済み

Borin Pier Luigi · 約1ヶ月前にレビュー済み

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

P Indhu · 約1ヶ月前にレビュー済み

Thorat (IN) Vaibhav · 約1ヶ月前にレビュー済み

Rathore (S01653) Nitesh · 約1ヶ月前にレビュー済み

Kang Xiao Qing · 約1ヶ月前にレビュー済み

GOOGLEUSER Revi · 約1ヶ月前にレビュー済み

Sharma Priyanka · 約1ヶ月前にレビュー済み

nagulapalli rajkumar · 約1ヶ月前にレビュー済み

Tolkachev Anton · 約1ヶ月前にレビュー済み

nice

Melendez Sergio · 約1ヶ月前にレビュー済み

Aviles Juan pablo · 約1ヶ月前にレビュー済み

Sinha Nidhi · 約1ヶ月前にレビュー済み

muy poco timepo

Aviles Juan pablo · 約1ヶ月前にレビュー済み

Sinha Nidhi · 約1ヶ月前にレビュー済み

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

Duque Neptali · 約1ヶ月前にレビュー済み

Mandlik Satin · 約1ヶ月前にレビュー済み

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.

Perala Sangeeth · 約1ヶ月前にレビュー済み

Saravia Felipe · 約1ヶ月前にレビュー済み

Kempski Christopher · 約1ヶ月前にレビュー済み

Robinson Roger · 約1ヶ月前にレビュー済み

Akula gopi krishna · 約1ヶ月前にレビュー済み

there is not enough time to complete these labs

Lewis Ramon · 約1ヶ月前にレビュー済み