Deploy a Compute Instance with a Remote Startup Script: Challenge Lab Reviews

Agustín M. · Reviewed over 7 years ago

Ciaran H. · Reviewed over 7 years ago

D Ther H. · Reviewed over 7 years ago

Jesus P. · Reviewed over 7 years ago

CHANDRASHEKAR C. · Reviewed over 7 years ago

1

Hung T. · Reviewed over 7 years ago

Good

Anil Kumar V. · Reviewed over 7 years ago

1

Hung T. · Reviewed over 7 years ago

Khiem L. · Reviewed over 7 years ago

Andres A. · Reviewed over 7 years ago

fine

RaviShankar R. · Reviewed over 7 years ago

howie Y. · Reviewed over 7 years ago

CHANDRASHEKAR C. · Reviewed over 7 years ago

Deepak M. · Reviewed over 7 years ago

Eduardo Antônio M. · Reviewed over 7 years ago

Daniel P. · Reviewed over 7 years ago

I discovered a bit too late the "run step" button, so I kept waiting lol

Gabriel P. · Reviewed over 7 years ago

Raju R. · Reviewed over 7 years ago

Vidina R. · Reviewed over 7 years ago

Richard F. · Reviewed over 7 years ago

Aleandro C. · Reviewed over 7 years ago

howie Y. · Reviewed over 7 years ago

would have been useful to point out that default compute service account had Editor access - so dont need to create one. and meta data has to be startup-script-url not startup-script (which GCP console creates)

Richard C. · Reviewed over 7 years ago

this lab sucked. give me a user that can actually set permissions - nothing worked! could only add service account access to bucket - couldnt edit service account permissions in IAM. complete waste of time!!!!

Richard C. · Reviewed over 7 years ago

Leonid Y. · Reviewed over 7 years ago