Closed muktaa closed 9 years ago
Another note: in the future we'll want to be able to get powershell modules from OneGet. So this resource should be able to handle that transparently -- we may need to think of what attributes are needed in the resource to specify module package names to OneGet with varying levels of qualification. We don't need to implement it, but our design should allow for that to be feasible (even if new attributes are required later).
@smurawski, can you take a look at this work in progerss on a powershell module resource in the powershell cookbook? We'd like your thoughts on the usability of this resource and cases that we may be missing if you have time.
Can we also update the README.md with some examples? Both the simplest example, and also something that specifies a few useful options (e.g. storing it in the user's module path rather than the system module path). And we should also test that . :)
A good example module to use would be psget: https://github.com/psget/psget/.
Another example for the readme would be one that retrieves the latest DSC resource kit.
We should also add some Chef Spec for this resource.