-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent ResourceHelper and Common cmdlets from being exported - Fixes #33 #34
Conversation
…urce kit modules. - Prevented ResourceHelper and Common module cmdlets from being exported to resolve conflicts with other resource modules.
Codecov Report
@@ Coverage Diff @@
## dev #34 +/- ##
====================================
+ Coverage 96% 96% +<1%
====================================
Files 7 7
Lines 1013 1020 +7
====================================
+ Hits 978 985 +7
Misses 35 35 |
@PlagueHO Did you branch this from the issue-31 working branch? Looks like you got those changes in here as well (?). Could you rebase against dev? |
And the same comment as in xStorage |
Doh! @johlju - you're right - I did. It was getting really late and I didn't check the branch I was in when I created the new one. Fixed now. Also changed the "Should not throw" to "Should Not Throw" |
I figured ;) No worries :) |
Reviewed 9 of 10 files at r1, 1 of 1 files at r2. Comments from Reviewable |
Thanks @johlju ! |
This resolves a high priority issue with newer versions of xNetworking, xCertificate, xStorage and xDFS conflicting with each other because the ResourceHelper cmdlets are being exported due to the way each resource imported them (using the PSD1 nested modules array).
This should be resolved in xNetworking, xStorage and xCertificate as well to ensure no other conflicts.
This also contains a new integration test that will check for any further conflicts between resource modules. At some point it might be possible to move this test into the DSCResource.Tests common tests to provide more comprehensive conflict prevention. However, because the conflicts will potentially be between three different modules the number of modules compared will have to go in over time.
This fixes #33
This change is