Anwendungen mit Apigee X modernisieren Rezensionen

Jose A. · Vor 14 Tage überprüft

lab env wasn't set up properly to create apigee resources

Sam H. · Vor 14 Tage überprüft

Nermin S. · Vor 14 Tage überprüft

Feiyu L. · Vor 14 Tage überprüft

mj s. · Vor 15 Tage überprüft

Hay un problema al validar el sharedFlow

Cristina S. · Vor 15 Tage überprüft

智文 陳. · Vor 15 Tage überprüft

Anibal H. · Vor 15 Tage überprüft

智文 陳. · Vor 16 Tage überprüft

Sastry I. · Vor 16 Tage überprüft

Sastry I. · Vor 16 Tage überprüft

Parth S. · Vor 16 Tage überprüft

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. · Vor 17 Tage überprüft

Sourojit S. · Vor 17 Tage überprüft

Mark Leo J. · Vor 18 Tage überprüft

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. · Vor 18 Tage überprüft

Yixuan C. · Vor 18 Tage überprüft

Lee D. · Vor 18 Tage überprüft

Blanca Margarita L. · Vor 20 Tage überprüft

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. · Vor 20 Tage überprüft

Shruti C. · Vor 20 Tage überprüft

Aniket A. · Vor 20 Tage überprüft

The curls from inside the vms don't work

Leonel N. · Vor 20 Tage überprüft

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. · Vor 21 Tage überprüft

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. · Vor 21 Tage überprüft