-
Type:
Bug
-
Status: Resolved
-
Priority:
Normal
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: PowerShell 2.1.5
-
Component/s: powershell
-
Labels:None
-
Template:
-
Acceptance Criteria:
-
Epic Link:
-
Team:Windows
-
Story Points:1
-
Sprint:Windows 2018-05-02, Windows 2018-05-09
-
Method Found:Needs Assessment
-
QA Risk Assessment:Needs Assessment
Basic Info
Module Version: 2.1.4
Puppet Version: N/A
OS Name/Version: Windows
With the exec resource, a timeout of 0 is allowed to mean infinite. While the timeout value is documented in the module README, it doesn't specifically state that the value deviates from the base exec provider. There are a few options for addressing this:
- a warning will be emitted with timeout set to `0`, with an automatic fallback to the default of `300` seconds instead
- some notes in the docs so that it’s more clear.
Current behavior
- When 0 it doesn't behave as expected, a really small timeout is set.
- The wrong exit code may be returned