You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is Your Feature Request Related To A Problem? Please describe.
Creating deployments for our manual testing purposes would be easier with this module, but because we need to be able to set all the advanced step settings, we're not currently able to do so easily with this module.
Describe The Solution. Why is it needed?
New-CcmDeploymentStep should have a -MachineContactTimeout parameter (I don't think the InMinutes suffix is strictly necessary, maybe we include that as an alias?) so we can set that setting as well on creating a deployment step.
Additional Context.
N/A
Related Issues
N/A
The text was updated successfully, but these errors were encountered:
Previously, ChocoCCM was unable to set the machine contact timeout.
With this change, we add the new parameter and allow users to select a
contact timeout according to their needs.
Just like in the CCM UI, the value is defaulted to zero.
Previously, ChocoCCM was unable to set the machine contact timeout.
With this change, we add the new parameter and allow users to select a
contact timeout according to their needs.
Just like in the CCM UI, the value is defaulted to zero.
vexx32
added a commit
to vexx32/ChocoCCM
that referenced
this issue
Jul 21, 2023
Is Your Feature Request Related To A Problem? Please describe.
Creating deployments for our manual testing purposes would be easier with this module, but because we need to be able to set all the advanced step settings, we're not currently able to do so easily with this module.
Describe The Solution. Why is it needed?
New-CcmDeploymentStep should have a
-MachineContactTimeout
parameter (I don't think theInMinutes
suffix is strictly necessary, maybe we include that as an alias?) so we can set that setting as well on creating a deployment step.Additional Context.
N/A
Related Issues
N/A
The text was updated successfully, but these errors were encountered: