(PDK-1432) Autogenerate PowerShell modules from code

[glennsarti]

Previously the PowerShell module code lived in the pdk-vanagon repository
however during release this required manual steps. This commit moves the
PowerShell module files to this repository and allows the use of ERB to update
them, for example, version and copyright year.

This commit also adds a beta PowerShell module which provides a much richer
and native PowerShell experience, by autogenerating from the CRI information.

[coveralls]

Coverage remained the same at 92.065% when pulling e31e0c2 on glennsarti:add-powershell-modules into d6aabe1 on puppetlabs:master.

[scotje]

Couple of minor things but looks good overall!

[jpogran]

Does module autoload conflict anything? I don't see any function or cmdlet name overlap, but the env variables are the same

[glennsarti]

Bouncing PR as a test

[glennsarti]

Does module autoload conflict anything? I don't see any function or cmdlet name overlap, but the env variables are the same

As far as I can tell, no. And the shared env vars are sane. Not sure what the motivation behind the question is?

Are you wondering if it should be one module?

Note that we need changes to pdk-vanagon for this to take effect.

[jpogran]

The reason I ask about the env variables is that some are different:

#old
$env:RUBY_DIR       = "$($env:DEVKIT_BASEDIR)\private\ruby\2.4.5"

#new
$env:RUBY_DIR       = "$($env:DEVKIT_BASEDIR)\private\ruby\2.4.4"

I was unsure if the module scope would save us, or are environment variables global scoped regardless of when/where they are created? The case I'm thinking is user loads old module, does some things, tries out new module and does some things, then goes back to old but ruby_dir is wrong now so it fails.

[glennsarti]

Ahh whoops yes...one of them is wrong. Based on older and new PDK versions

Env will be process level

[glennsarti]

@jpogran Fixed the env vars issue. I wonder if I should make that an interpolated value so at least it's consistent...

[jpogran]

I don't think that's required for this PR. I think that is more part of the work to get the beta module to a version 1

[jpogran]

[scotje]

@glennsarti It looks like @jpogran approved this, so is there anything else we are waiting on before we merge this?