Apigee Lab 5: Protecting Against JSON Content Attacks Reviews

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. · Reviewed over 3 years ago

Jun Zhe N. · Reviewed over 3 years ago

Heidi E. · Reviewed over 3 years ago

Jose Alfron B. · Reviewed over 3 years ago

Clarisse Myles P. · Reviewed over 3 years ago

Francis G. · Reviewed over 3 years ago

Akshay B. · Reviewed over 3 years ago

McKinley A. · Reviewed over 3 years ago

Lucas G. · Reviewed over 3 years ago

Guillermo P. · Reviewed over 3 years ago

Princess Lyca L. · Reviewed over 3 years ago

Eshan K. · Reviewed over 3 years ago

Varsha K. · Reviewed over 3 years ago

Felipe R. · Reviewed over 3 years ago

Kevin R. · Reviewed over 3 years ago

Piyush S. · Reviewed over 3 years ago

Udaya I. · Reviewed over 3 years ago

Vijay R. · Reviewed over 3 years ago

Ankit P. · Reviewed over 3 years ago

Akhil A. · Reviewed over 3 years ago

Pradeep P. · Reviewed over 3 years ago

suneetha m. · Reviewed over 3 years ago

Gayatri S. · Reviewed over 3 years ago

Vijayalaxmi N. · Reviewed over 3 years ago

Lavanya J. · Reviewed over 3 years ago