Mengotomatiskan Deployment Infrastruktur Menggunakan Deployment Manager Ulasan

Tilak B. · Diulas sekitar 6 tahun lalu

another great lab

Ashton N. · Diulas sekitar 6 tahun lalu

정환 승. · Diulas sekitar 6 tahun lalu

Alisher B. · Diulas sekitar 6 tahun lalu

Adebiyi T. · Diulas sekitar 6 tahun lalu

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. · Diulas sekitar 6 tahun lalu

Denis P. · Diulas sekitar 6 tahun lalu

Thouseefuddin M. · Diulas sekitar 6 tahun lalu

lilianlhli l. · Diulas sekitar 6 tahun lalu

Harsh D. · Diulas sekitar 6 tahun lalu

Nicholas O. · Diulas sekitar 6 tahun lalu

Kingsley Ikechukwu O. · Diulas sekitar 6 tahun lalu

lilianlhli l. · Diulas sekitar 6 tahun lalu

Harsh D. · Diulas sekitar 6 tahun lalu

Good

Ayodeji O. · Diulas sekitar 6 tahun lalu

Jonathan E. · Diulas sekitar 6 tahun lalu

Thouseefuddin M. · Diulas sekitar 6 tahun lalu

Benoit M. · Diulas sekitar 6 tahun lalu

Ruwini S. · Diulas sekitar 6 tahun lalu

Jelena M. · Diulas sekitar 6 tahun lalu

Nishchal A. · Diulas sekitar 6 tahun lalu

Finally managed to crack the config.yaml format

Korah Jacob C. · Diulas sekitar 6 tahun lalu

Alexandra A. · Diulas sekitar 6 tahun lalu

Elmo A. · Diulas sekitar 6 tahun lalu