Apigee X を使った API の公開 のレビュー

Tank Kritansh · 6ヶ月前にレビュー済み

jadhav sanket · 6ヶ月前にレビュー済み

哈 哈 · 6ヶ月前にレビュー済み

gerardo diaz georgina maria del rosario · 6ヶ月前にレビュー済み

Vargas Cristopher · 6ヶ月前にレビュー済み

Patro B Saloni · 6ヶ月前にレビュー済み

Arivazhagan Surya · 6ヶ月前にレビュー済み

M Rajnarayanan · 6ヶ月前にレビュー済み

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

Quintos Arturo · 6ヶ月前にレビュー済み

Tamer Mohamed · 6ヶ月前にレビュー済み

Zaitoon Ahmed · 6ヶ月前にレビュー済み

Neto Manuel · 6ヶ月前にレビュー済み

Arcade Humaidi · 6ヶ月前にレビュー済み

Janiszewski Damian · 6ヶ月前にレビュー済み

Dantas Leandro · 6ヶ月前にレビュー済み

Gamez Armenta 90270529 Marco Antonio · 6ヶ月前にレビュー済み

Gamez Armenta 90270529 Marco Antonio · 6ヶ月前にレビュー済み

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

Hofmann Thomas · 6ヶ月前にレビュー済み

神垣 眞哉 · 6ヶ月前にレビュー済み

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}

Deschênes Antoine · 6ヶ月前にレビュー済み

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>

Deschênes Antoine · 6ヶ月前にレビュー済み

Trifan Liviu-Teodor · 6ヶ月前にレビュー済み

too many clicks

Hristov Vladimir · 6ヶ月前にレビュー済み

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

Janiszewski Damian · 6ヶ月前にレビュー済み

Birajdar Sangamesh · 6ヶ月前にレビュー済み