That seems a convention in all of our APIs. For APIs with support sort of
on-behalf-of semantics, currently we are always using (account, domainId)
parameter pair, where account requires accountName. You can see similar
patterns in list APIs. Of course, we can change this, but may need to be
in nex
Hi,
We need to deploy VMs on behalf of certain users and surprisingly it's not
possible to use accountid with deployvirtualmachine, the actual name of the
account needs to be used.
Anyone knows why this is and if it can be changed? It's quite awkward since
everything else in the API seems to re
