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

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. · 评论7 months之前

Damian J. · 评论7 months之前

Leandro D. · 评论7 months之前

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

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

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

Thomas H. · 评论7 months之前

眞哉 神. · 评论7 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. · 评论7 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. · 评论7 months之前

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

too many clicks

Vladimir H. · 评论7 months之前

the required resources like Cloud Run service and service account were not provisioned and lab cannot be continued

Damian J. · 评论7 months之前

Sangamesh B. · 评论7 months之前

Arunkumar P. · 评论7 months之前

You should have us use the new Apigee.

Lucas S. · 评论7 months之前

Amit D. · 评论7 months之前

Lillian S. · 评论7 months之前

Yoshitha V. · 评论7 months之前

Christian L. · 评论7 months之前

Aryav V. · 评论7 months之前

Mariana T. · 评论7 months之前