Opinie (Modernizing Applications with Apigee X)

Jose A. · Sprawdzono 14 dni temu

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

Sam H. · Sprawdzono 14 dni temu

Nermin S. · Sprawdzono 14 dni temu

Feiyu L. · Sprawdzono 14 dni temu

mj s. · Sprawdzono 15 dni temu

Hay un problema al validar el sharedFlow

Cristina S. · Sprawdzono 15 dni temu

智文 陳. · Sprawdzono 15 dni temu

Anibal H. · Sprawdzono 15 dni temu

智文 陳. · Sprawdzono 16 dni temu

Sastry I. · Sprawdzono 16 dni temu

Sastry I. · Sprawdzono 16 dni temu

Parth S. · Sprawdzono 16 dni temu

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. · Sprawdzono 17 dni temu

Sourojit S. · Sprawdzono 17 dni temu

Mark Leo J. · Sprawdzono 18 dni temu

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. · Sprawdzono 18 dni temu

Yixuan C. · Sprawdzono 18 dni temu

Lee D. · Sprawdzono 18 dni temu

Blanca Margarita L. · Sprawdzono 20 dni temu

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. · Sprawdzono 20 dni temu

Shruti C. · Sprawdzono 20 dni temu

Aniket A. · Sprawdzono 20 dni temu

The curls from inside the vms don't work

Leonel N. · Sprawdzono 20 dni temu

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. · Sprawdzono 21 dni temu

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. · Sprawdzono 21 dni temu