关于“Integrate Cloud Run Functions with Firestore”的评价

Rahul R. · 评论about 1 month之前

Jithish J. · 评论about 1 month之前

Mohd Hakimi M. · 评论about 1 month之前

Kripesh K. · 评论about 1 month之前

Muhammad Zunnurain H. · 评论about 1 month之前

Oskar Ś. · 评论about 1 month之前

Leonel N. · 评论about 1 month之前

This part was incorrect, had to fix the code myself: ``` Write the function code In the editor, add the following code below in the firestore_functions/index.js file: ```

Mitchell T. · 评论about 1 month之前

Sanjay R. · 评论about 1 month之前

Liquan Y. · 评论about 1 month之前

Mayur K. · 评论about 1 month之前

Mayur K. · 评论about 1 month之前

Eric T. · 评论about 1 month之前

Sajja V. · 评论about 1 month之前

When creating functions error is thrown, although the function is created successfully upon retry, it is still reducing points in the progress leading to incompletion : ERROR: (gcloud.functions.deploy) OperationError: code=3, message=Could not create or update Cloud Run service newcustomer, Container Healthcheck failed. Quota exceeded for total allowable memory per project per region.

Santhosh N. · 评论about 1 month之前

This lab is not working as expected please check this one

Srinivas A. · 评论about 1 month之前

Madhu K. · 评论about 1 month之前

Bhuvan Krishna S. · 评论about 1 month之前

2nd to last task never fully credited me even though i reviewed the configuration and it was exactly as described in the lab. It also functioned correctly, adding the fullname field so not clear what acceptance criteria it is using. 2nd attempt the lastname piece worked fine. Then the last steps of reading a secret failed. Even though I correctly confirmed the IAM setup and that the secret was save. It complained when deploying the updated function that is could not find the key. I waited for significant amount time but it seems like the overall platform is flaky. third time a charm, went through

Cory R. · 评论about 1 month之前

2nd to last task never fully credited me even though i reviewed the configuration and it was exactly as described in the lab. It also functioned correctly, adding the fullname field so not clear what acceptance criteria it is using. 2nd attempt the lastname piece worked fine. Then the last steps of reading a secret failed. Even though I correctly confirmed the IAM setup and that the secret was save. It complained when deploying the updated function that is could not find the key. I waited for significant amount time but it seems like the overall platform is flakey.

Cory R. · 评论about 1 month之前

2nd to last task never fully credited me even though i reviewed the configuration and it was exactly as described in the lab. It also functioned correctly, adding the fullname field so not clear what acceptance criteria it is using.

Cory R. · 评论about 1 month之前

Ana G. · 评论about 1 month之前

Madhu K. · 评论about 1 month之前

Mujahedul I. · 评论about 1 month之前

Rayane J. · 评论about 1 month之前