关于“Apigee Lab 5: Protecting Against JSON Content Attacks”的评价

Jose F. · 已于 over 3 years前审核

Suprabhat V. · 已于 over 3 years前审核

Mounika T. · 已于 over 3 years前审核

Tauqeer A. · 已于 over 3 years前审核

Shaik H. · 已于 over 3 years前审核

Velpula V. · 已于 over 3 years前审核

Karthika K. · 已于 over 3 years前审核

solumtochukwu o. · 已于 over 3 years前审核

Madhusudan M. · 已于 over 3 years前审核

Pedro David M. · 已于 over 3 years前审核

Sergio E. · 已于 over 3 years前审核

The instructions for the lab were fine, but when testing the curl commands I kept getting 404 not found errors from apigee when trying to create an order.

Isaiah M. · 已于 over 3 years前审核

Joshua G. · 已于 over 3 years前审核

Tanya H. · 已于 over 3 years前审核

Jorenz Gabrielle Y. · 已于 over 3 years前审核

Mark V. · 已于 over 3 years前审核

Aditya N. · 已于 over 3 years前审核

Samir M. · 已于 over 3 years前审核

export API_KEY=$(curl -q -s -H "Authorization: Bearer $(gcloud auth print-access-token)" -X GET "https://apigee.googleapis.com/v1/organizations/${GOOGLE_CLOUD_PROJECT}/developers/joe@example.com/apps/retail-app" | jq --raw-output '.credentials[0].consumerKey'); echo "export API_KEY=${API_KEY}" >> ~/.profile; echo "API_KEY=${API_KEY}" { "error": { "code": 400, "message": "unable to parse organization from resource name", "status": "INVALID_ARGUMENT" } } The runtime instance was available but project was not set in the shell, had to manually add it "gcloud config set project {ID}"

César M. · 已于 over 3 years前审核

Jun Zhe N. · 已于 over 3 years前审核

Heidi E. · 已于 over 3 years前审核

Jose Alfron B. · 已于 over 3 years前审核

Clarisse Myles P. · 已于 over 3 years前审核

Francis G. · 已于 over 3 years前审核

Akshay B. · 已于 over 3 years前审核