Skip to content
David Ebbo edited this page Sep 23, 2015 · 2 revisions

Where does Resource Explorer get its metadata

It learns about existing APIs from a mix of sources:

From Azure Resource Manager

ARM has an API to list resource providers, and the registered resource types within it. The API looks like this:

/subscriptions/{sub}/providers

This is the primary mechanism that Explorer uses to discover things. The downside is that it is not very complete. e.g. it doesn't show the shape of the payload that needs to be sent to a given API.

From Swagger specs

For a small set of providers like Web Apps, Explorer uses a spec that gives it a full definition of the API available for the provider. This gives much richer information than what we can get from ARM, but right now it's not available for most providers.

Explorer tweets from the community

Cool tweets