Opinie (Konfigurowanie środowiska programistycznego w Google Cloud: laboratorium-wyzwanie)

Binisa G. · Sprawdzono 26 dni temu

Aditya M. · Sprawdzono 26 dni temu

ashish s. · Sprawdzono 26 dni temu

Pablo y. · Sprawdzono 26 dni temu

Julio Cesar L. · Sprawdzono 26 dni temu

Suphlay K. · Sprawdzono 26 dni temu

Mike G. · Sprawdzono 26 dni temu

Souravi B. · Sprawdzono 26 dni temu

Коваль С. · Sprawdzono 26 dni temu

SEBASTIAN P. · Sprawdzono 26 dni temu

The lab assume to many things that if you are not a devops you can do it, without help. Its a shame

Facundo Gonzalo U. · Sprawdzono 26 dni temu

Sejal C. · Sprawdzono 26 dni temu

Yeison J. · Sprawdzono 27 dni temu

Sahil L. · Sprawdzono 27 dni temu

Royston P. · Sprawdzono 27 dni temu

Luis Enrique S. · Sprawdzono 27 dni temu

I created the Cloud Function successfully with the correct trigger, it worked, the thumbnail was created, and yet the lab failed to recognise that the funciton was created and therefore did not give me the correct score.

Felipe C. · Sprawdzono 27 dni temu

Rafael T. · Sprawdzono 27 dni temu

Antonio F. · Sprawdzono 27 dni temu

Nadim B. · Sprawdzono 27 dni temu

Mohammad Faheem A. · Sprawdzono 27 dni temu

Valentina G. · Sprawdzono 27 dni temu

Pedro A. M. · Sprawdzono 27 dni temu

The lab experience was extremely frustrating and consumed a huge amount of time and credits for issues unrelated to the actual exercise. Main problems encountered: * The `index.js` code box silently truncated the code. Part of the file disappeared without warning, causing broken deployments and syntax errors. I lost around 10 minutes debugging something caused by the UI itself. * The account/session repeatedly disconnected during the lab. * Identity confirmation/password verification frequently failed even with the correct credentials. * The web console became practically unusable, forcing me to complete most tasks entirely through Cloud Shell CLI. * IAM permission propagation delays are excessive. Even trivial role assignments required waiting 2–3 minutes before becoming effective. * Eventarc / Pub/Sub / Cloud Functions permissions are very fragile and poorly initialized in fresh lab projects. * Trigger creation for Cloud Storage functions failed multiple times because required service accounts and permissions were not automatically configured. * Uploading files to Cloud Storage and waiting for triggers/functions to execute also introduced long delays, making debugging extremely slow. * Error messages were often incomplete or misleading, especially around Eventarc Service Agents and Cloud Storage Pub/Sub permissions. Suggestions for improvement: * Ensure code editors never truncate pasted code silently. * Pre-provision Eventarc and required service agents before the lab starts. * Reduce IAM propagation delays or add automatic retries during deployment. * Improve error diagnostics for Cloud Functions Gen2 + Eventarc + Cloud Storage integrations. * Stabilize authentication/session handling in temporary Qwiklabs accounts. * Provide CLI-first instructions for advanced labs instead of relying heavily on the unstable UI. The technical content of the lab is good, but the platform reliability and infrastructure delays make the experience unnecessarily difficult.

Gianluigi M. · Sprawdzono 27 dni temu

Mike G. · Sprawdzono 27 dni temu