关于“Publishing APIs with Apigee X”的评价

Siddhartha G. · 评论6 months之前

apigee was not working, could not call, in checking eval group I don't see any IPs, checked 2 times

Евгений Л. · 评论6 months之前

Siddhartha G. · 评论6 months之前

Kritansh T. · 评论6 months之前

sanket j. · 评论6 months之前

哈 哈. · 评论6 months之前

georgina maria del rosario g. · 评论6 months之前

Cristopher V. · 评论6 months之前

B Saloni P. · 评论6 months之前

Surya A. · 评论6 months之前

Rajnarayanan M. · 评论6 months之前

The test on the console cannot be done because send a 404 and the instance was on the same subnet internal

Arturo Q. · 评论6 months之前

Mohamed T. · 评论6 months之前

Ahmed Z. · 评论6 months之前

Manuel N. · 评论6 months之前

Humaidi A. · 评论6 months之前

Damian J. · 评论6 months之前

Leandro D. · 评论6 months之前

90270529 Marco Antonio G. · 评论6 months之前

90270529 Marco Antonio G. · 评论6 months之前

classic agigee not supported. Unable to add a policy. There is no Security configuration in the preFlow step :-(

Thomas H. · 评论6 months之前

眞哉 神. · 评论6 months之前

Missing steps in Task 1 will make Apigee fail to call Cloud Run: gcloud iam service-accounts create apigee-internal-access \ --display-name="Service account for internal access by Apigee proxies" \ --project=${GOOGLE_CLOUD_PROJECT} gcloud run services add-iam-policy-binding simplebank-rest \ --member="serviceAccount:apigee-internal-access@${GOOGLE_CLOUD_PROJECT}.iam.gserviceaccount.com" \ --role=roles/run.invoker --region=europe-west1 \ --project=${GOOGLE_CLOUD_PROJECT}

Antoine D. · 评论6 months之前

Lab is broken. - `apigee-internal-access` Service Account to use with the API proxy wasn't created. - ssh to the instance was failing with `Permission denied (publickey).` - tesing the API after "API products" were setup would fail with <h2>Your client does not have permission to get URL <code>/customers</code> from this server.</h2>

Antoine D. · 评论6 months之前

Liviu-Teodor T. · 评论6 months之前