-
Notifications
You must be signed in to change notification settings - Fork 0
adding Invoke-DscResource RFC Draft #1
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
base: master
Are you sure you want to change the base?
Conversation
Co-Authored-By: Steve Lee <[email protected]>
thanks Joey Co-Authored-By: Joey Aiello <[email protected]>
I think we should indicate that calls to Invoke-DscResource in different sessions or jobs should not block each other and be able to execute at the same time. It already feels like this would be the case, but it's worth mentioning because I believe that is a current limitation in 5.1. |
updating RFC as per comments from Travis, Steve & Kevin
@KevinMarquette Running in different session or jobs at the same time is a bad idea, but I agree that the cmdlet should not block it. |
* updating RFC with updated discussion/comments * Update 1-Draft/RFCXXXX-RFC-Invoke-DscResource.md Co-Authored-By: Travis Plunk <[email protected]> * Update 1-Draft/RFCXXXX-RFC-Invoke-DscResource.md * updating GET result as per Travis comment
properties to property Co-Authored-By: Travis Plunk <[email protected]>
properties to property Co-Authored-By: Travis Plunk <[email protected]>
properties to property Co-Authored-By: Travis Plunk <[email protected]>
- expanding LCM/WMI - reboot and $Global:DSCMachineStatus - superfluous text
Creating PR for discussing initial draft.