Develop and Secure APIs with Apigee X: Challenge Lab avis
Chargement...
Aucun résultat.

Google Cloud Skills Boost

Mettez en pratique vos compétences dans la console Google Cloud

Develop and Secure APIs with Apigee X: Challenge Lab avis

3027 avis

Bridget L. · Examiné il y a environ 3 ans

Jason C. · Examiné il y a environ 3 ans

Task 2 throws error but responses returned are as expected

Ayush A. · Examiné il y a environ 3 ans

finally managed to get it completed but error messages or problems can be explained in a better manner. thanks for fixing the issues

Aakash S. · Examiné il y a environ 3 ans

Manikanta A. · Examiné il y a environ 3 ans

Manikanta A. · Examiné il y a environ 3 ans

Srikant B. · Examiné il y a environ 3 ans

its ok

Edgar L. · Examiné il y a environ 3 ans

Srikant B. · Examiné il y a environ 3 ans

task 2 and 3 are in bug

alaaeddine z. · Examiné il y a environ 3 ans

Dmytro K. · Examiné il y a environ 3 ans

Task 2 , Completion validation is quite weird kind of, It took a lot of time in understanding how the evaluation works, eventhough the proxy was working fine, Rating/Review section helped me :D , regarding the double quotes in w.r.t JS file. The error messages aren't that helpful also.

Sujith T. · Examiné il y a environ 3 ans

This lab was definitely a "challenge" as the name stands. I find it very hard to someone who doesn't have experience with Apigee to pass on this lab on the first attempt, because there are some requirements that we haven't learned during the course. I have some difficultly specially with the "jsonPath" template, because I was having some difficulty figuring the second part of the command where we have to point to the variable (response.content for example). I gave two stars because I got very frustrated for two reasons: 1) Despite the fact that my API was working as intended, I was still getting errors saying that my AssignMessage policy was incorrect. That was because I had some line breaks in there because of indentation that I added, after I put the entire json in a single line it worked. I again had this errors with my JavaScript file because I was using single quotes instead of double quotes. Kind of dumb but I failed on my second attempt because I was debugging this and trying to understand why I was getting a wrong answer despite the fact that my API was working. 2) Apigee code panel is very bad! It doesn't have autocomplete, doesn't have highlight, do only basic validation. Like, come on Google, you can do better than that! It's specially frustrating because I need to wait for the API to deploy, start a debug session, sometimes the debug session takes some time before the requests start showing up... Well, very time consuming! I really love Apigee and it's functionalities, but the code editor needs some serious improvements. I know that Google already have code editor components out there, they just need to add those to Apigee!

Anderson P. · Examiné il y a environ 3 ans

Pablo P. · Examiné il y a environ 3 ans

Mario C. · Examiné il y a environ 3 ans

Saurabh D. · Examiné il y a environ 3 ans

Saurabh D. · Examiné il y a environ 3 ans

Saurabh D. · Examiné il y a environ 3 ans

Oksana V. · Examiné il y a environ 3 ans

Suhani K. · Examiné il y a environ 3 ans

Raja K. · Examiné il y a environ 3 ans

Please, add additional info to Task 2 for the step with creating JS-BuildLanguagesResponse policy, js resource file should be named "BuildLanguagesResponse.js", in other case Check would failed.

Ivan B. · Examiné il y a environ 3 ans

Ivan B. · Examiné il y a environ 3 ans

Ivan B. · Examiné il y a environ 3 ans

James M. · Examiné il y a environ 3 ans

Nous ne pouvons pas certifier que les avis publiés proviennent de consommateurs qui ont acheté ou utilisé les produits. Les avis ne sont pas vérifiés par Google.