Créer une application sans serveur qui permet de produire des fichiers PDF à l'aide de Cloud Run avis

Yousif A. · Examiné il y a environ un mois

Jesus Humberto A. · Examiné il y a environ un mois

André M. · Examiné il y a environ un mois

Pier Luigi B. · Examiné il y a environ un mois

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

Indhu P. · Examiné il y a environ un mois

Vaibhav T. · Examiné il y a environ un mois

Nitesh R. · Examiné il y a environ un mois

Xiao Qing K. · Examiné il y a environ un mois

Revi G. · Examiné il y a environ un mois

Priyanka S. · Examiné il y a environ un mois

rajkumar n. · Examiné il y a environ un mois

Anton T. · Examiné il y a environ un mois

nice

Sergio M. · Examiné il y a environ un mois

Juan pablo A. · Examiné il y a environ un mois

Nidhi S. · Examiné il y a environ un mois

muy poco timepo

Juan pablo A. · Examiné il y a environ un mois

Nidhi S. · Examiné il y a environ un mois

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

Neptali D. · Examiné il y a environ un mois

Satin M. · Examiné il y a environ un mois

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. · Examiné il y a environ un mois

Felipe S. · Examiné il y a environ un mois

Christopher K. · Examiné il y a environ un mois

Roger R. · Examiné il y a environ un mois

gopi krishna A. · Examiné il y a environ un mois

there is not enough time to complete these labs

Ramon L. · Examiné il y a environ un mois