Integrate Cloud Run Functions with Firestore Reviews

Rahul R. · Reviewed 18 days ago

Jithish J. · Reviewed 18 days ago

Mohd Hakimi M. · Reviewed 18 days ago

Kripesh K. · Reviewed 18 days ago

Muhammad Zunnurain H. · Reviewed 19 days ago

Oskar Ś. · Reviewed 19 days ago

Leonel N. · Reviewed 19 days ago

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. · Reviewed 20 days ago

Sanjay R. · Reviewed 20 days ago

Liquan Y. · Reviewed 20 days ago

Mayur K. · Reviewed 20 days ago

Mayur K. · Reviewed 20 days ago

Eric T. · Reviewed 20 days ago

Sajja V. · Reviewed 20 days ago

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. · Reviewed 20 days ago

This lab is not working as expected please check this one

Srinivas A. · Reviewed 20 days ago

Madhu K. · Reviewed 20 days ago

Bhuvan Krishna S. · Reviewed 20 days ago

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. · Reviewed 21 days ago

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. · Reviewed 21 days ago

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. · Reviewed 21 days ago

Ana G. · Reviewed 21 days ago

Madhu K. · Reviewed 21 days ago

Mujahedul I. · Reviewed 22 days ago

Rayane J. · Reviewed 22 days ago