Hi Prachi, Sorry for bringing this up so late -
Since the feature is not yet released and the API not out in the wild I thought perhaps the name updateVmAffinityGroup makes more sense as updateAffinityGroup. This will make it conform with the rest of the APIs associated with AffinityGroups(create/delete/list). Just makes it easier to identify the resource the API is acting upon and more intuitive. Does the update API do something different that warrants the odd naming? Thanks, -- Prasanna., ------------------------ Powered by BigRock.com
