VMware PowerCLI
The Best User Interface for your VMware Datacenter!
The Best User Interface for your VMware Datacenter!
The Best User Interface for your VMware Datacenter!
I have PowerCLI 6.5.2 installed and have the following folders in my modulepath:
VMware.VimAutomation.Cis.Core
VMware.VimAutomation.Common
VMware.VimAutomation.Core
VMware.VimAutomation.HA
VMware.VimAutomation.HorizonView
VMware.VimAutomation.License
VMware.VimAutomation.Sdk
VMware.VimAutomation.Srm
VMware.VimAutomation.Vds
VMware.VimAutomation.vROps
Modules like VMware.VimAutomation.Common export zero commands.This is cumbersome when writing scripts to add each of these to my #requires statements. Maybe break these up by discipline that you would/could install separately?
E.g. PowerCLI.vCenter
E.g. PowerCLI.vRops
E.g PowerCLI.HorizonView
Brandon Lundt
Although there are no exported cmdlets in some modules, they function as libs for multiple modules. Because of this, they need to be separate. These lib modules never need to be imported, as they are automatically imported from their dependent module.
@Luc Dekens
Yes that would fit the bill.
Doesn't a '#requires VMware.PowerCLI', and module auto-loading fit the bill?
I'd also like to that that it'd be helpful if versioning was more..... consistent. I know there's times where a particular module may not be getting any TLC because nothing really changed, but... it'd be handy dandy if I didn't have to guess if what's in PowerCLI Gallery was actually accurate with what's on my local machine....