We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, names are used in the routes for VMs and hosts, i.e. the constraints: { id: /.*/ } snippets.
constraints: { id: /.*/ }
This also means all vms are under /vms/vm.
/vms/vm
Does vSphere return IDs that could be used instead?
The text was updated successfully, but these errors were encountered:
vsphere cli output:
Name : creation-test PowerState : PoweredOn Notes : Guest : creation-test: NumCpu : 1 CoresPerSocket : 1 MemoryMB : 1024 MemoryGB : 1 VMHostId : HostSystem-host-82 VMHost : ibmesx14.eaalab.hpi.uni-potsdam.de VApp : FolderId : Folder-group-v117 Folder : Pending archivings ResourcePoolId : ResourcePool-resgroup-141 ResourcePool : Resources HARestartPriority : ClusterRestartPriority HAIsolationResponse : AsSpecifiedByCluster DrsAutomationLevel : AsSpecifiedByCluster VMSwapfilePolicy : Inherit VMResourceConfiguration : CpuShares:Normal/1000 MemShares:Normal/10240 Version : v13 PersistentId : 502ccc43-b097-680e-5256-699a33033d57 GuestId : otherGuest UsedSpaceGB : 1,1075638402253389358520507812 ProvisionedSpaceGB : 2,1075643049553036689758300781 DatastoreIdList : {Datastore-datastore-28} ExtensionData : VMware.Vim.VirtualMachine CustomFields : {[password, ]} Id : VirtualMachine-vm-407 Uid : /VIServer=swt.local\[email protected]:443/VirtualMachine=Virtu alMachine-vm-407/ Client : VMware.VimAutomation.ViCore.Impl.V1.VimClient
Sorry, something went wrong.
No branches or pull requests
Currently, names are used in the routes for VMs and hosts, i.e. the
constraints: { id: /.*/ }
snippets.This also means all vms are under
/vms/vm
.Does vSphere return IDs that could be used instead?
The text was updated successfully, but these errors were encountered: