Configurer un environnement de développement d'applications sur Google Cloud : atelier challenge avis

Binisa G. · Examiné il y a 26 jours

Aditya M. · Examiné il y a 26 jours

ashish s. · Examiné il y a 26 jours

Pablo y. · Examiné il y a 26 jours

Julio Cesar L. · Examiné il y a 26 jours

Suphlay K. · Examiné il y a 26 jours

Mike G. · Examiné il y a 26 jours

Souravi B. · Examiné il y a 26 jours

Коваль С. · Examiné il y a 26 jours

SEBASTIAN P. · Examiné il y a 26 jours

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. · Examiné il y a 26 jours

Sejal C. · Examiné il y a 27 jours

Yeison J. · Examiné il y a 27 jours

Sahil L. · Examiné il y a 27 jours

Royston P. · Examiné il y a 27 jours

Luis Enrique S. · Examiné il y a 27 jours

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. · Examiné il y a 27 jours

Rafael T. · Examiné il y a 27 jours

Antonio F. · Examiné il y a 27 jours

Nadim B. · Examiné il y a 27 jours

Mohammad Faheem A. · Examiné il y a 27 jours

Valentina G. · Examiné il y a 27 jours

Pedro A. M. · Examiné il y a 27 jours

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. · Examiné il y a 27 jours

Mike G. · Examiné il y a 27 jours