Cloud Run Functions: Qwik Start – Befehlszeile Rezensionen

Dipali J. · Vor 4 Monate überprüft

mahajaishree R. · Vor 4 Monate überprüft

VENNELA T. · Vor 4 Monate überprüft

Mitsuki Y. · Vor 4 Monate überprüft

komal k. · Vor 4 Monate überprüft

Taresh I. · Vor 4 Monate überprüft

Ajay N. · Vor 4 Monate überprüft

Vinit P. · Vor 4 Monate überprüft

Vanteddu Haritha Jyothi .. · Vor 4 Monate überprüft

egional Access Boundary HTTP request failed after retries: response_data={'error': {'code': 404, 'message': 'Account not found for email: 54379ce39f|student-03-1aaf41fb75ee@qwiklabs.net', 'status': 'NOT_FOUND'}}, retryable_error=False Regional Access Boundary HTTP request failed after retries: response_data={'error': {'code': 404, 'message': 'Account not found for email: 54379ce39f|student-03-1aaf41fb75ee@qwiklabs.net', 'status': 'NOT_FOUND'}}, retryable_error=False ERROR: (gcloud.functions.describe) ResponseError: status=[404], code=[], message=[Resource 'projects/qwiklabs-gcp-04-930a2368ca6b/locations/asia-south1/functions/nodejs-pubsub-function' was not found]

Isaac O. · Vor 4 Monate überprüft

Alvaro G. · Vor 4 Monate überprüft

Alvaro G. · Vor 4 Monate überprüft

. . .. · Vor 4 Monate überprüft

Rittwikkk G. · Vor 4 Monate überprüft

Renaldy I. · Vor 4 Monate überprüft

Prafullakumar G. · Vor 4 Monate überprüft

JAYESH A. · Vor 4 Monate überprüft

sandeep d. · Vor 4 Monate überprüft

Betty Z. · Vor 4 Monate überprüft

25EU08R0438 - S. · Vor 4 Monate überprüft

SARTHAK S. · Vor 4 Monate überprüft

Claire H. · Vor 4 Monate überprüft

SANGVI C. · Vor 4 Monate überprüft

Nery C. · Vor 4 Monate überprüft

Hi Support Team, I am writing to report a severe issue regarding the backend configuration in the Cloud Functions Gen2 laboratories. When attempting to deploy a Node.js Gen2 Cloud Function via the gcloud CLI using an event trigger (--trigger-topic), the deployment consistently fails with the following sequence of errors: Regional Access Boundary HTTP request failed after retries (Error 404: Account not found for email...) ERROR: (gcloud.functions.deploy) ResponseError: status=[400], message=[Service account service-XXXXXXXXXXXX@gcp-sa-pubsub.iam.gserviceaccount.com does not exist.] Root Cause Analysis: Pub/Sub Identity Creation Bug: The gcloud functions deploy command automatically tries to initialize the Pub/Sub service agent identity and bind the roles/iam.serviceAccountTokenCreator role on the fly. Regional Access Boundary Clash: Because the project enforces a strict constraints/gcp.resourceLocations policy (forcing deployments into specific regions like europe-west3), the underlying IAM API requests triggered by the CLI tool break the lab's proxy boundaries, stripping the student session credentials mid-command (Gaia id not found). To bypass this and complete the lab via CLI, I had to manually invoke gcloud beta services identity create --service=pubsub.googleapis.com and manually bind the IAM policies before running the deployment command in the exact authorized region. Please review the automated service account creation and the Regional Access Boundary proxy filters for this lab, as it makes the standard CLI instructions completely broken for students. Best regards, Rodrigo

Rodrigo A. · Vor 4 Monate überprüft