It is a supported scenario to use a Profile, but use a single set of resource models and operations outside the profile. This supports a couple of scenarios:
Using a new feature like Managed Disks without breaking the rest of my code
Allowing for the scenario where one RP is 'frozen' for a particular Azure installation
Right now, you can instantiate a ResourceOperations class using the AzureClient, but I wonder if we shouldn't have extension methods (GetManagedDiskOperations(this IAzureClient client) that would mean simply including the correct namespace to discover).
These operations would be decorated onto the client, so they could be accessed off of the client simply by including that API version operation's namespace, right?
It is a supported scenario to use a Profile, but use a single set of resource models and operations outside the profile. This supports a couple of scenarios:
Right now, you can instantiate a ResourceOperations class using the AzureClient, but I wonder if we shouldn't have extension methods (
GetManagedDiskOperations(this IAzureClient client)
that would mean simply including the correct namespace to discover).