Issue #3764 has been updated by Alan Barrett.
Nigel Kersten wrote:
> Should we instead make this more flexible and allow it to set the equivalent
> of the log level?
That might be useful, but I am not sure that there is a log level equivalent to
"fail" (although we could invent one). I don't just want a message in the log,
I want other resources that depend on the notify to fail due to a failed
dependency.
<pre>
class foo {
notify { "foo is not yet implemented for this environment":
fail => true,
}
}
class bar {
require foo
# everything in class bar should be skipped due to a failed dependency
...
}
</pre>
----------------------------------------
Feature #3764: Add "fail" parameter to notify resource
http://projects.puppetlabs.com/issues/3764
Author: Alan Barrett
Status: Needs design decision
Priority: Normal
Assigned to: Luke Kanies
Category: functions
Target version:
Affected version: 0.25.4
Keywords:
Branch:
I often want a puppet manifest to result in an error on the client. This is
useful for marking "to do" items, where users should be reminded of
shortcomings in the manifest.
I have added a "fail" parameter to the notify resource. Usage is as follows:
<pre>
notify { "Feature X is not yet implemented":
fail => true,
}
</pre>
I attach a patch to implement this feature, but I have not added test cases.
It would be nice to have "onlyif" and "unless" parameters, but I have not
implemented those.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
