From 4572ad810bf7c2e3468fcee11b3cf54b9fa19b76 Mon Sep 17 00:00:00 2001 From: Peter Souter Date: Wed, 8 Apr 2015 18:05:01 +0100 Subject: [PATCH] (docs) Clarification on unless and only Could probably clearer that the `unless` and `only` parameters have all the same parameters as the main exec, not just the path. (DOCUMENT-319) --- lib/puppet/type/exec.rb | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/lib/puppet/type/exec.rb b/lib/puppet/type/exec.rb index e2ac02c2c3d..2270f9da330 100644 --- a/lib/puppet/type/exec.rb +++ b/lib/puppet/type/exec.rb @@ -413,7 +413,8 @@ def check(value) `grep` determines it's already there. Note that this command follows the same rules as the main command, - which is to say that it must be fully qualified if the path is not set. + such as which user and group it's run as. + This also means it must be fully qualified if the path is not set. It also uses the same provider as the main command, so any behavior that differs by provider will match. EOT @@ -456,7 +457,9 @@ def check(value) This would run `logrotate` only if that test returned true. Note that this command follows the same rules as the main command, - which is to say that it must be fully qualified if the path is not set. + such as which user and group it's run as. + This also means it must be fully qualified if the path is not set. + It also uses the same provider as the main command, so any behavior that differs by provider will match.