Migrar um banco de dados MySQL para o Google Cloud SQL: laboratório com desafio avaliações

Peter V. · Revisado há 25 days

Payal L. · Revisado há 25 days

Gauri L. · Revisado há 25 days

Gokul K. · Revisado há 25 days

Labs are great. But the UI of is awfull. Fix it please

Egor S. · Revisado há 25 days

instruction for --authorized-networks not clear (use range and not ip)

Yura T. · Revisado há 25 days

Vikranth R. · Revisado há 25 days

Luiz F. · Revisado há 26 days

Antonio Whinnes G. · Revisado há 26 days

Varsha P. · Revisado há 26 days

Hendy Chandra H. · Revisado há 26 days

Error

Sohail S. · Revisado há 26 days

localhost being used instead of the actual ip address is kind of annoying.

Deeksha C. · Revisado há 26 days

shyamkumar m. · Revisado há 26 days

darren c. · Revisado há 26 days

doesn't work (task 5) and cannot understand why (have tried everything)

Deeksha C. · Revisado há 26 days

Loic N. · Revisado há 26 days

David D. · Revisado há 26 days

Vitalii L. · Revisado há 26 days

RAUSHAN Y. · Revisado há 26 days

Mukesh Kumar Y. · Revisado há 26 days

John L. · Revisado há 26 days

Shawn M. · Revisado há 26 days

Jason E. · Revisado há 27 days

This lab has a validation bug in Task 3. The Cloud SQL instance automatically authorizes RFC 1918 IP ranges (including 10.142.0.3 from the blog VM), but the lab's scoring system fails to detect this implicit authorization and requires manual addition of the IP, which the Google Cloud API explicitly blocks. All manual steps were completed successfully and the WordPress blog is fully functional with the Cloud SQL database. Please fix the validation logic to recognize automatically authorized IP ranges.

Alexandre C. · Revisado há 27 days