PSModule resource does not support installing side-by-side versioned modules

[brywang-msft]

From @rdean716 on May 11, 2016 19:57

Because the the Name parameter is Key, the PSModule resource cannot be used to download two versions of the same module. It would be nice if the Key parameter could also accept the module specification format for scenarios when more than one version of a module is required for a node.

Consider the following.

    PSModule 'tooling-1.0.0.21'
    {
        Name = 'tooling'
        Repository = 'InternalNuget'
        RequiredVersion = '1.0.0.21'
        Ensure = 'Present'
        InstallationPolicy = 'Trusted'
    }

    PSModule 'tooling-1.0.0.28'
    {
        Name = 'tooling'
        Repository = 'InternalNuget'
        RequiredVersion = '1.0.0.28'
        Ensure = 'Present'
        InstallationPolicy = 'Trusted'
    }

The resulting error:

Test-ConflictingResources : A conflict was detected between resources '[PSModule]tooling-1.0.0.21 
(C:\Users\Bob\Documents\config.ps1::16::5::PSModule)' and '[PSModule]tooling-1.0.0.28 
(C:\Users\Bob\Documents\config.ps1::26::5::PSModule)' in node 'localhost'.  Resources have identical key properties but there are differences in the following non-key properties: 'RequiredVersion'. Values '1.0.0.21' don't match values '1.0.0.28'. Please update these property values so that they are identical in both cases.

Thanks for taking a look at this.

Copied from original issue: PowerShell/PackageManagementProviderResource#11