关于“利用 Apigee X 对应用进行现代化改造”的评价

Jose A. · 已于 14 days前审核

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

Sam H. · 已于 14 days前审核

Nermin S. · 已于 14 days前审核

Feiyu L. · 已于 14 days前审核

mj s. · 已于 15 days前审核

Hay un problema al validar el sharedFlow

Cristina S. · 已于 15 days前审核

智文 陳. · 已于 15 days前审核

Anibal H. · 已于 15 days前审核

智文 陳. · 已于 16 days前审核

Sastry I. · 已于 16 days前审核

Sastry I. · 已于 16 days前审核

Parth S. · 已于 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. · 已于 17 days前审核

Sourojit S. · 已于 17 days前审核

Mark Leo J. · 已于 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. · 已于 18 days前审核

Yixuan C. · 已于 18 days前审核

Lee D. · 已于 18 days前审核

Blanca Margarita L. · 已于 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. · 已于 20 days前审核

Shruti C. · 已于 20 days前审核

Aniket A. · 已于 20 days前审核

The curls from inside the vms don't work

Leonel N. · 已于 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. · 已于 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. · 已于 21 days前审核