Créer une application sans serveur qui permet de produire des fichiers PDF à l'aide de Cloud Run avis
49295 avis
Juan Diego N. · Examiné il y a 3 mois
Ian S. · Examiné il y a 3 mois
Done
Anil B. · Examiné il y a 3 mois
Peter I. · Examiné il y a 3 mois
Jeyson G. · Examiné il y a 3 mois
Yousif A. · Examiné il y a 3 mois
Jesus Humberto A. · Examiné il y a 3 mois
André M. · Examiné il y a 3 mois
Pier Luigi B. · Examiné il y a 3 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 3 mois
Vaibhav T. · Examiné il y a 3 mois
Nitesh R. · Examiné il y a 3 mois
Xiao Qing K. · Examiné il y a 3 mois
Revi G. · Examiné il y a 3 mois
Priyanka S. · Examiné il y a 3 mois
rajkumar n. · Examiné il y a 3 mois
Anton T. · Examiné il y a 3 mois
nice
Sergio M. · Examiné il y a 3 mois
Juan pablo A. · Examiné il y a 3 mois
Nidhi S. · Examiné il y a 3 mois
muy poco timepo
Juan pablo A. · Examiné il y a 3 mois
Nidhi S. · Examiné il y a 3 mois
Dockerfile seems is not properly updated to run when deploying in cloud run.
Neptali D. · Examiné il y a 3 mois
Satin M. · Examiné il y a 3 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 3 mois
Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.