Como implantar aplicativos no Google Cloud avaliações

66268 avaliações

veeramani g. · Revisado há about 1 year

FAZIMA K. · Revisado há about 1 year

מור א. · Revisado há about 1 year

Christian Eduardo M. · Revisado há about 1 year

so fun

PD-SRE y. · Revisado há about 1 year

In "Task 4. Deploy to Cloud Run", image was built and pushed to artifact registry, but assessment module didn't recognise the cloud run image on artifact registry.

Satya P. · Revisado há about 1 year

Cynthia C. · Revisado há about 1 year

good

Raja R. · Revisado há about 1 year

good

Prabu M. · Revisado há about 1 year

GREAT!

Igor C. · Revisado há about 1 year

Ismar B. · Revisado há about 1 year

paths in task 3 and 4 are wrong. instead of cd ~/gcp-course/training-data-analyst/courses/design-process/deploying-apps-to-gcp it shall be cd ~/gcp-course/deploying-apps-to-gcp

Tomasz W. · Revisado há about 1 year

1. Lab have many mistakes and typos. Cite: @app.route("/") def main(): model = {"title" "Hello App Engine"} return render_template('index.html', model=model) Should be: @app.route("/") def main(): model = {"title": "Hello App Engine"} return render_template('index.html', model=model) Missing semicolon ":" between the strings "title" "Hello App Engine" will lead to errors 500 then deployed. I assume those errors and/ or output of the deployed app version not actually checked in the lab - nobody noticed. This typo is repeated two more times: ------------ @app.route("/") def main(): model = {"title" "Hello Kubernetes Engine"} return render_template('index.html', model=model) @app.route("/") def main(): model = {"title" "Hello Cloud Run"} return render_template('index.html', model=model) 2. some task specs are confusing: Cite: "To migrate production traffic to version two, click Split Traffic at the top. Change the version to two, and click Save." but proportions of the split is not specified (and not checked in the lab), default proportion of the split is 0 - traffic will go to ver1 not to ver2 3. paths are not correct "Add a file named kubernetes-config.yaml to the training-data-analyst/courses/design-process/deploying-apps-to-gcp folder." .... "cd ~/gcp-course/training-data-analyst/courses/design-process/deploying-apps-to-gcp gcloud builds submit --tag us-central1-docker.pkg.dev/$DEVSHELL_PROJECT_ID/devops-demo/devops-image:v0.2 ." "cd ~/gcp-course/training-data-analyst/courses/design-process/deploying-apps-to-gcp gcloud builds submit --tag us-central1-docker.pkg.dev/$DEVSHELL_PROJECT_ID/devops-demo/cloud-run-image:v0.1 ." Those steps will not work - we never mentioned the folder "training-data-analyst" before in the lab, originally we created a path ~/gcp-course/deploying-apps-to-gcp.

Yuri G. · Revisado há about 1 year

Gabriel G. · Revisado há about 1 year

Sundar M. · Revisado há about 1 year

Rizky Eka Briliansyah C. · Revisado há about 1 year

There was some confusion in the folder structure. The instructions for the Kubernetes part did not match the ret of the lab.

Fredrik K. · Revisado há about 1 year

Vidya M. · Revisado há about 1 year

Brenda Y. · Revisado há about 1 year

Sandeep N. · Revisado há about 1 year

Aneika L. · Revisado há about 1 year

good

Prabu M. · Revisado há about 1 year

more time needed...abrobtly ended the lab...gave a new login...all my progress is lost. Tried to reach the support, no use...feeling helpless

Sivasankaran N. · Revisado há about 1 year

Muhammad A. · Revisado há about 1 year

Mustafa T. · Revisado há about 1 year

Não garantimos que as avaliações publicadas sejam de consumidores que compraram ou usaram os produtos. As avaliações não são verificadas pelo Google.