Automating the Deployment of Infrastructure Using Deployment Manager Reviews

54677 reviews

Kamil O. · Reviewed almost 6 years ago

Jason B. · Reviewed almost 6 years ago

Daniel A. · Reviewed almost 6 years ago

Thouseefuddin M. · Reviewed almost 6 years ago

Tilak B. · Reviewed almost 6 years ago

another great lab

Ashton N. · Reviewed almost 6 years ago

정환 승. · Reviewed almost 6 years ago

Alisher B. · Reviewed almost 6 years ago

Adebiyi T. · Reviewed almost 6 years ago

In Cloud Shell (accessed from the GCP console), there's no reference to a "Code Editor" - you just get prompted to "Open Editor" - as I was using ChromeOS I got a warning about how the editor wouldn't "play nicely" Sure enough, as the lab progressed I found issues with indentation and cut/paste from the Lab instructions, this contributed to my failure to complete the Lab. Might need to attempt the Lab using a different device (not really a Qwiklabs issue though) I re-tried the Lab (using the same ChromeOS based device) and still encountered issues at the "deployment creation" stage - the instructions suggest trouble-shooting and it was clear enough that Deployment Manager was unable to parse either the config OR template files I'd edited. Although exactly whether it was one or both files was not clear from the console output (which I've copied below)... ERROR: (gcloud.deployment-manager.deployments.update) Error in Operation [operation-1602069902442-5b112f770be86-b3313db7-4ffef4f0]: errors: - code: MANIFEST_EXPANSION_USER_ERROR location: /deployments/dminfra/manifests/manifest-1602069902762 message: |- Manifest expansion encountered the following errors: while parsing a block mapping in "<unicode string>", line 2, column 3: - name: mynet-us-vm ^ expected <block end>, but found '<block mapping start>' in "<unicode string>", line 6, column 6: zone: us-central1-a ^ Resource: config ....so I resorted to uploading the sample files into the Lab's CloudShell VM and renamed them to configQW.yaml and instance-templateQW.jinja respectively. The deployment then worked OK using the uploaded files (as expected) so a quick browse of the uploaded files indicated blank lines between the different resource entries in the yaml file whilst the indentations in the updated template file didn't match how they were rendered by my Chrome browser in the Lab instructions

Anthony D. · Reviewed almost 6 years ago

Denis P. · Reviewed almost 6 years ago

Thouseefuddin M. · Reviewed almost 6 years ago

lilianlhli l. · Reviewed almost 6 years ago

Harsh D. · Reviewed almost 6 years ago

Nicholas O. · Reviewed almost 6 years ago

Kingsley Ikechukwu O. · Reviewed almost 6 years ago

lilianlhli l. · Reviewed almost 6 years ago

Harsh D. · Reviewed almost 6 years ago

Good

Ayodeji O. · Reviewed almost 6 years ago

Jonathan E. · Reviewed almost 6 years ago

Thouseefuddin M. · Reviewed almost 6 years ago

Benoit M. · Reviewed almost 6 years ago

Ruwini S. · Reviewed almost 6 years ago

Jelena M. · Reviewed almost 6 years ago

We do not ensure the published reviews originate from consumers who have purchased or used the products. Reviews are not verified by Google.