Opinie (App Dev - Deploying an API for the Quiz Application: Node.js)

not found

Ignacio A. · Sprawdzono ponad rok temu

$ gcloud functions deploy process-feedback --runtime nodejs14 --trigger-topic feedback --source ./function --stage-bucket $GCLOUD_BUCKET --entry-point subscribe As of this Cloud SDK release, new functions will be deployed as 2nd gen functions by default. This is equivalent to currently deploying new with the --gen2 flag. Existing 1st gen functions will not be impacted and will continue to deploy as 1st gen functions. You can disable this behavior by explicitly specifying the --no-gen2 flag or by setting the functions/gen2 config property to 'off'. To learn more about the differences between 1st gen and 2nd gen functions, visit: https://cloud.google.com/functions/docs/concepts/version-comparison WARNING: Node.js 14 is no longer supported by the Node.js community as of 30 April, 2023. Node.js 14 will be decommissioned on 2025-01-30. As of 2025-01-30 you will no longer be able to deploy your Cloud Functions using nodejs14. We recommend you to upgrade to the latest version of Node.js as soon as possible. Service account [service-424103739061@gcp-sa-pubsub.iam.gserviceaccount.com] is missing the role [roles/iam.serviceAccountTokenCreator]. Pub/Sub needs this role to create identity tokens. For more details, please see https://cloud.google.com/pubsub/docs/push#authentication Bind the role [roles/iam.serviceAccountTokenCreator] to service account [service-424103739061@gcp-sa-pubsub.iam.gserviceaccount.com]? (Y/n)? Y ERROR: (gcloud.functions.deploy) ResponseError: status=[400], code=[Ok], message=[Service account service-424103739061@gcp-sa-pubsub.iam.gserviceaccount.com does not exist.]

Luc R. · Sprawdzono ponad rok temu

Marc R. · Sprawdzono ponad rok temu

Florentin A. · Sprawdzono ponad rok temu

Ivan A. · Sprawdzono ponad rok temu

Not working service account is not created still

Márton D. · Sprawdzono ponad rok temu

Marcelo C. · Sprawdzono ponad rok temu

Rajneesh R. · Sprawdzono ponad rok temu

Unable to progress, the cloud function doesn't gets deployed and the progress is stuck there.

Kumar A. · Sprawdzono ponad rok temu

Suraj N. · Sprawdzono ponad rok temu

César F. · Sprawdzono ponad rok temu

DAVID R. · Sprawdzono ponad rok temu

Learning material was great but there is issues with "prepare_environment.sh" script. Had to do workarounds to complete the lab..

Mindaugas Š. · Sprawdzono ponad rok temu

When running '. prepare_environment.sh' I get the error as mentioned in the notes. ERROR: (gcloud.functions.deploy) ResponseError: status=[400], code=[Ok], message=[Service account service-499472191276@gcp-sa-pubsub.iam.gserviceaccount.com does not exist.] I rerun the deploy command - gcloud functions deploy process-feedback --runtime nodejs14 --trigger-topic feedback --source ./function --stage-bucket $GCLOUD_BUCKET --entry-point subscribe but get the same error again. I've tried 3 times, leaving it for about 10 mins before trying the deploy again in case it's a delay with the setup but still get the error. In the console there are these messages for the service account. Service account [service-499472191276@gcp-sa-pubsub.iam.gserviceaccount.com] is missing the role [roles/iam.serviceAccountTokenCreator]. Pub/Sub needs this role to create identity tokens. For more details, please see https://cloud.google.com/pubsub/docs/push#authentication Bind the role [roles/iam.serviceAccountTokenCreator] to service account [service-499472191276@gcp-sa-pubsub.iam.gserviceaccount.com]? (Y/n)? Y then I get the error.

Rob T. · Sprawdzono ponad rok temu

Mohammad Ataur R. · Sprawdzono ponad rok temu

Raghunandan N. · Sprawdzono ponad rok temu

Raghunandan N. · Sprawdzono ponad rok temu

Michel-Hugues M. · Sprawdzono ponad rok temu

Alexandru B. · Sprawdzono ponad rok temu

Zakaria H. · Sprawdzono ponad rok temu

arnaud b. · Sprawdzono ponad rok temu

Marcel E. · Sprawdzono ponad rok temu

Joseph E. · Sprawdzono ponad rok temu

Rajneesh R. · Sprawdzono ponad rok temu

Rajneesh R. · Sprawdzono ponad rok temu