VMware PowerCLI

The Best User Interface for your VMware Datacenter!

Simplify the Module name/Structure

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
  • Aug 31 2017
  • Attach files
  • Steve Kaplan commented
    September 1, 2017 00:44

    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....

  • Luc Dekens commented
    September 1, 2017 16:30

    Doesn't a '#requires VMware.PowerCLI', and module auto-loading fit the bill?

  • Brandon Lundt commented
    September 5, 2017 14:09

    @Luc Dekens

    Yes that would fit the bill.