Modernizing Applications with Apigee X Reviews

智文 陳. · Reviewed 5 days ago

Anibal H. · Reviewed 5 days ago

智文 陳. · Reviewed 6 days ago

Sastry I. · Reviewed 6 days ago

Sastry I. · Reviewed 7 days ago

Parth S. · Reviewed 7 days ago

There were 2 bugs with this lab, 1 of which I was able to workaround. In the section "Test the API proxy" I was never able to successfully call the API after adding the <Authentication> section to the target endpoint xml. This was the error: curl -i -k "https://eval.example.com/bank/v1/atms/spruce-goose" HTTP/2 500 content-type: application/json x-request-id: 20034795-2f15-4147-9a9c-9f04562bade8 content-length: 344 date: Fri, 08 May 2026 17:47:50 GMT via: 1.1 google {"fault":{"faultstring":"Google token generation has failed. Please refer to https:\/\/cloud.google.com\/apigee\/docs\/api-platform\/reference\/policies\/service-callout-policy#runtime-errors for troubleshooting tips on GoogleTokenGenerationFailure errors.","detail":{"errorcode":"messaging.adaptors.http.filter.GoogleTokenGenerationFailure"}}} I tried troubleshooting the error but every possible cause for this error listed in the google documentation did not resolve this issue. The second bug I encountered was in the "Add a Service Callout policy" section which, if you follow the instructions exactly up to that point, you'll run into an issue where the "Add" button is disabled (grayed out) and it is impossible to add the policy. Oddly enough, this bug was resolved by refreshing the page in my browser and trying again.

Barclay I. · Reviewed 7 days ago

Sourojit S. · Reviewed 8 days ago

Mark Leo J. · Reviewed 8 days ago

You did not give service-[Project-Number]@gcp-sa-apigee.iam.gserviceaccount.com to have Role "Service Account Token Creator" and it will give error for <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <TargetEndpoint name="default">   <Description/>   <FaultRules/>   <PreFlow name="PreFlow">     <Request/>     <Response/>   </PreFlow>   <PostFlow name="PostFlow">     <Request/>     <Response/>   </PostFlow>   <Flows/>   <HTTPTargetConnection>     <Properties/>     <URL>https://simplebank-rest-z6cmrsuiia-uk.a.run.app</URL>     <Authentication>       <GoogleIDToken>         <Audience>https://simplebank-rest-z6cmrsuiia-uk.a.run.app</Audience>       </GoogleIDToken>     </Authentication>   </HTTPTargetConnection> </TargetEndpoint>

Thanasit V. · Reviewed 9 days ago

Yixuan C. · Reviewed 9 days ago

Lee D. · Reviewed 9 days ago

Blanca Margarita L. · Reviewed 10 days ago

Apigee was not provisioned at the start, and trying to do so manually did not work with this error: constraints/gcp.resourceLocations Restarting the lab did make it work. However I was unable to finish final testing due to another error with api token generation.

Devin M. · Reviewed 10 days ago

Shruti C. · Reviewed 11 days ago

Aniket A. · Reviewed 11 days ago

The curls from inside the vms don't work

Leonel N. · Reviewed 11 days ago

No I had an issue, I have a 500 response instead of 200 and I dont know how to fix it I did the exercice twice

Hélène S. · Reviewed 11 days ago

No I had an issue, I have a 500 response instead of 200 and I dont know how to fix it I did the exercice twice

Hélène S. · Reviewed 11 days ago

Hélène S. · Reviewed 11 days ago

AYAKA W. · Reviewed 11 days ago

David C. · Reviewed 12 days ago

Joselito S. · Reviewed 13 days ago

Alexander Yerson R. · Reviewed 13 days ago

雅登 大. · Reviewed 14 days ago