Building Event-Driven Orchestration on Google Cloud Reviews

Salai Selva Kumari S. · Reviewed 9 месяцев ago

task10 有错

Dennis C. · Reviewed 9 месяцев ago

Cristina S. · Reviewed 9 месяцев ago

Dhibika B. · Reviewed 9 месяцев ago

Step #1: [builder] === Node.js - Runtime (google.nodejs.runtime@1.0.0) === Step #1: [builder] 2024/12/02 03:09:35 [DEBUG] GET https://dl.google.com/runtimes/ubuntu2204/nodejs/version.json Step #1: [builder] ***** CACHE MISS: "nodejs" Step #1: [builder] Installing Node.js v22.11.0. Step #1: [builder] 2024/12/02 03:09:36 [DEBUG] GET https://dl.google.com/runtimes/ubuntu2204/nodejs/nodejs-22.11.0.tar.gz Step #1: [builder] === Node.js - Npm (google.nodejs.npm@1.1.0) === Step #1: [builder] ***** CACHE MISS: "npm_modules" Step #1: [builder] Installing application dependencies. Step #1: [builder] -------------------------------------------------------------------------------- Step #1: [builder] Running "npm ci --quiet --no-fund --no-audit (NODE_ENV=production)" Step #1: [builder] npm error code EUSAGE Step #1: [builder] npm error Step #1: [builder] npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing. Step #1: [builder] npm error Step #1: [builder] npm error Missing: @google-cloud/firestore@6.8.0 from lock file Step #1: [builder] npm error Missing: @google-cloud/storage@6.12.0 from lock file Step #1: [builder] npm error Missing: @google/events@5.4.0 from lock file Step #1: [builder] npm error Missing: cloudevents@6.0.3 from lock file Step #1: [builder] npm error Missing: express@4.21.1 from lock file Step #1: [builder] npm error Missing: fast-deep-equal@3.1.3 from lock file Step #1: [builder] npm error Missing: functional-red-black-tree@1.0.1 from lock file Step #1: [builder] npm error Missing: google-gax@3.6.1 from lock file Step #1: [builder] npm error Missing: protobufjs@7.4.0 from lock file Step #1: [builder] npm error Missing: @google-cloud/paginator@3.0.7 from lock file Step #1: [builder] npm error Missing: @google-cloud/projectify@3.0.0 from lock file Step #1: [builder] npm error Missing: @google-cloud/promisify@3.0.1 from lock file Step #1: [builder] npm error Missing: abort-controller@3.0.0 from lock file Step #1: [builder] npm error Missing: async-retry@1.3.3 from lock file

Dennis C. · Reviewed 9 месяцев ago

Jan U. · Reviewed 9 месяцев ago

There is an error in extract-image-metadata: TypeError: Cannot read properties of undefined (reading 'text') at exports.extract_image_metadata (/workspace/index.js:39:50) at /layers/google.nodejs.functions-framework/functions-framework/node_modules/@google-cloud/functions-framework/build/src/function_wrappers.js:100:29 at process.processTicksAndRejections (node:internal/process/task_queues:77:11)

Volodymyr K. · Reviewed 9 месяцев ago

尚也 佐. · Reviewed 9 месяцев ago

Task 10. Trigger a service to delete image files and metadata has a error during creation eventarc for delete image. I had to create it using: gcloud eventarc triggers create image-delete-trigger... The error was: "Cannot access API run.googleapis.com in project qwiklabs-gcp-04-e275cec0c415"

Szymon G. · Reviewed 9 месяцев ago

Volodymyr K. · Reviewed 9 месяцев ago

Pavithra H. · Reviewed 9 месяцев ago

Pavithra H. · Reviewed 9 месяцев ago

Wicaksono A. · Reviewed 9 месяцев ago

Wicaksono A. · Reviewed 9 месяцев ago

Enough time is not given to complete the lab. It has so many services, more time is required to review everything.

Himanshi R. · Reviewed 9 месяцев ago

Andrew-john A. · Reviewed 9 месяцев ago

problems with api run

Peter T. · Reviewed 9 месяцев ago

The lab is not showing option delete-image

Ayushi K. · Reviewed 9 месяцев ago

Mohit B. · Reviewed 9 месяцев ago

could not create the delete trigger :-(

Thomas H. · Reviewed 9 месяцев ago

this sucks im legit just copying and pasting shit nonstop

Devarshee R. · Reviewed 9 месяцев ago

Malleswara-A R. · Reviewed 9 месяцев ago

La experiencia en este lab fue mala, me salian muchos errores y no puede avanzar de manera adecuada, se perdió mucho tiempo en los 5 intentos que realice, no pude terminar el lab comparto uno de los tantos problemas que tuve, se necesita mejorar este lab y no pagare por hacerlo de nuevo. student_03_c2fef8791f33@cloudshell:~/code/cloud-run/delete-image (qwiklabs-gcp-02-9b5b3fef7934)$ export DELETE_SERVICE_REGION=us-west1 export DELETE_SERVICE_NAME=delete-image export GENERATED_IMAGES_BUCKET=generated-images-${GOOGLE_CLOUD_PROJECT} cd ~/code/cloud-run/delete-image gcloud config set run/region ${DELETE_SERVICE_REGION} gcloud config set run/platform managed gcloud run deploy ${DELETE_SERVICE_NAME} \ --source . \ --no-allow-unauthenticated \ --max-instances=1 \ --update-env-vars GENERATED_IMAGES_BUCKET=${GENERATED_IMAGES_BUCKET} Updated property [run/region]. Updated property [run/platform]. Building using Buildpacks and deploying container to Cloud Run service [delete-image] in project [qwiklabs-gcp-02-9b5b3fef7934] region [us-west1] X Building and deploying new service... Building Container. OK Uploading sources... - Building Container... Logs are available at [https://console.cloud.google.com/cloud-build/builds/50c3523f-81ab-4338-bce6-ac7e36258e01?project=621678382785]. . Creating Revision... . Routing traffic... Deployment failed ERROR: (gcloud.run.deploy) Build failed; check build logs for details

Josephe Yair S. · Reviewed 9 месяцев ago

a bug in the end on the final step run.googleapis.com

Jesus Damian T. · Reviewed 9 месяцев ago

unable to complete task 10 as described. when setting up the trigger the delete-image service was not listed as a service under Cloud Run. In fact there were no services listed under Cloud Run. There was some kind of API error shown. I was able to build the trigger by going to the Cloud Run page, selecting the delete-image service and using the option to add a trigger from there.

John J. · Reviewed 9 месяцев ago