Intégrer Cloud Run Functions à Firestore avis

Kripesh K. · Examiné il y a 18 jours

Muhammad Zunnurain H. · Examiné il y a 19 jours

Oskar Ś. · Examiné il y a 19 jours

Leonel N. · Examiné il y a 19 jours

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. · Examiné il y a 19 jours

Sanjay R. · Examiné il y a 19 jours

Liquan Y. · Examiné il y a 19 jours

Mayur K. · Examiné il y a 20 jours

Eric T. · Examiné il y a 20 jours

Sajja V. · Examiné il y a 20 jours

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. · Examiné il y a 20 jours

This lab is not working as expected please check this one

Srinivas A. · Examiné il y a 20 jours

Madhu K. · Examiné il y a 20 jours

Bhuvan Krishna S. · Examiné il y a 20 jours

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. · Examiné il y a 21 jours

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. · Examiné il y a 21 jours

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. · Examiné il y a 21 jours

Ana G. · Examiné il y a 21 jours

Madhu K. · Examiné il y a 21 jours

Mujahedul I. · Examiné il y a 21 jours

Rayane J. · Examiné il y a 22 jours

Andrew G. · Examiné il y a 22 jours

great

Gurpreet K. · Examiné il y a 22 jours

Areyci H. · Examiné il y a 22 jours