Como modernizar aplicativos com a Apigee X avaliações

Jose A. · Revisado há 14 days

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

Sam H. · Revisado há 14 days

Nermin S. · Revisado há 14 days

Feiyu L. · Revisado há 14 days

mj s. · Revisado há 15 days

Hay un problema al validar el sharedFlow

Cristina S. · Revisado há 15 days

智文 陳. · Revisado há 15 days

Anibal H. · Revisado há 15 days

智文 陳. · Revisado há 16 days

Sastry I. · Revisado há 16 days

Sastry I. · Revisado há 16 days

Parth S. · Revisado há 16 days

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. · Revisado há 17 days

Sourojit S. · Revisado há 17 days

Mark Leo J. · Revisado há 18 days

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. · Revisado há 18 days

Yixuan C. · Revisado há 18 days

Lee D. · Revisado há 18 days

Blanca Margarita L. · Revisado há 20 days

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. · Revisado há 20 days

Shruti C. · Revisado há 20 days

Aniket A. · Revisado há 20 days

The curls from inside the vms don't work

Leonel N. · Revisado há 20 days

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. · Revisado há 21 days

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. · Revisado há 21 days