[PUP-3485] Exec "command" Attribute Only Autorequires First Path in String Created: 2014/10/17 Updated: 2015/01/26 Resolved: 2015/01/26
|Component/s:||Types and Providers|
|Affects Version/s:||PUP 3.7.1|
|Reporter:||Ryan Gard||Assignee:||Josh Cooper|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
If a user uses an "command" attribute with multiple paths only the first will be evaluated for autorequire. Example below:
It would be more helpful for the end user to have all paths in the "command" attribute be evaluated for autorequire.
The Puppet agent run should complete successfully.
The Puppet agent run fails:
|Comment by Charlie Sharpsteen [ 2014/10/17 ]|
Personally, I don't think Exec autorequire should attempt to be this clever. What if there are arguments between the executable and the path? How do we determine that the command line has gotten sufficiently complex that autorequire processing should give up? As a user, I would prefer explicit requires over an autorequire subject to subtle bugs and complicated edge cases.
|Comment by Josh Cooper [ 2015/01/26 ]|
+1 to "should not attempt to be this clever", going to close this.