Flesh out Azure API Docs with return types with methods and members, object documentation, possible input values
Using a single API call as an example:
This seems self-explanatory. However, we're left to figure out on our own:
- The type of the returned object
- Its methods and members
Some other API docs don't mention what possible values are for some inputs.
This particular doc mentions how to check the status of this cmdlet (by using Get-AzureRMAutomationModule and checking the ProvisioningStatus member of the return object), but it fails to mention all of the possible values of this member and what they mean.
In all of these cases, it becomes necessary to reverse engineer what's what, which adds development time--adding iterations dedicated to understanding objects and values instead of what the code is actually doing.