关于“预配 Apigee X 评估组织”的评价

4611 条评价

Jai Shankar K. · 已于 18 days前审核

Jai Shankar K. · 已于 18 days前审核

Yurii K. · 已于 18 days前审核

Iperezc G. · 已于 19 days前审核

Dmytro S. · 已于 21 days前审核

YOGESH D. · 已于 22 days前审核

Eduardo H. · 已于 22 days前审核

Mark Anthony N. · 已于 23 days前审核

YOGESH D. · 已于 23 days前审核

Rehan B. · 已于 24 days前审核

Rehan B. · 已于 24 days前审核

Sanjay G. · 已于 26 days前审核

Michelle T. · 已于 28 days前审核

Kiran R. · 已于 30 days前审核

Matthew K. · 已于 about 1 month前审核

Achmad Z. · 已于 about 1 month前审核

so bad

Yalçın T. · 已于 about 1 month前审核

Dahnia M. · 已于 about 1 month前审核

Enrique N. · 已于 about 1 month前审核

rizky a. · 已于 about 1 month前审核

Kira D. · 已于 about 1 month前审核

david g. · 已于 about 1 month前审核

Zaid S. · 已于 about 1 month前审核

The Apigee evaluation instance was automatically provisioned in us-west1. The effective constraints/gcp.resourceLocations policy allows us-east1, but does not allow us-west1. The Access Routing wizard automatically attempts to create the managed instance group apigee-proxy-us-west1 and fails. The wizard does not provide a location selector. The temporary account has roles/owner, but it does not have the setOrgPolicy permission, so the policy cannot be adjusted. The internal access test completed successfully with HTTP 200 and "Hello, Guest!", but Task 5 cannot create the external load

Wellington O. · 已于 about 1 month前审核

The Apigee evaluation instance was automatically provisioned in us-west1. The effective constraints/gcp.resourceLocations policy allows us-east1, but does not allow us-west1. The Access Routing wizard automatically attempts to create the managed instance group apigee-proxy-us-west1 and fails. The wizard does not provide a location selector. The temporary account has roles/owner, but it does not have the setOrgPolicy permission, so the policy cannot be adjusted. The internal access test completed successfully with HTTP 200 and "Hello, Guest!", but Task 5 cannot create the external load

Wellington O. · 已于 about 1 month前审核

我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。