Hey y'all - Here are some key documentation enhancements over the past month. And as always, here’s how to send us direct feedback on the documentation:
https://community.apigee.com/articles/10274/sending-feedback-on-apigee-documentation.html. Your feedback truly makes a difference.
Happy digital transforming!
Learning Edge
We've started a library of quick command-line-with-Trace samples designed to let newer Edge users learn by doing. Each sample, which illustrates a different concept, takes less than a minute to deploy and run and is deployed to the same sample
learn-edge proxy as a new revision. This keeps your organization uncluttered while letting you explore the code in previous samples/revisions. Get more information here:
https://community.apigee.com/content/kbentry/29429/for-new-edge-developers-introducing-learn-edge.ht...
Errors and fault handling
- Policy errors are now listed in a single topic (in addition to being listed on each policy reference topic), letting you view them all in one place. Here's the new reference:
http://docs.apigee.com/api-services/content/error-code-reference
We've also started adding guidance on what policy errors mean and how to handle them. We'll gradually expand coverage.
-
Fault handling can be tricky to implement, but our topic update includes more comprehensive coverage about fault handling concepts, behavior, implementation, and best practices:
http://docs.apigee.com/api-services/content/fault-handling
This doc update was the outgrowth of a
community thread, which is a perfect example of how community participation helps everyone.
Edge for Private Cloud
We're also keeping you abreast of what's changed in the Edge for Private Cloud docs. Periodically we'll post an article in the Community that lists documentation changes and enhancements. Bookmark this page and keep checking back for updated information:
https://community.apigee.com/articles/26606/41601-and-41605-edge-for-private-cloud-doc-updated.html
LinkedIn
Twitter