Issue #1878 has been updated by Daniel Pittman.

Status changed from Needs Decision to Rejected

I am inclined to this that this is a bad change, at least in the specific 
circumstance cited: there are lots of reasons you might fail to fetch the file 
from the server, including the file being removed, access control forbidding 
access, SSL changes, and so forth.  Unless we distinguish those, triggering 
some exec action feels very much like a case of working around a problem that 
you shouldn't have.

If we had use cases that were not contrived, or similarly working around 
problems, I would accept that, but it otherwise seems better solved with a more 
targetted feature (eg: invoke some notification action), or fixing the root 
cause (eg: file is not accessible)
----------------------------------------
Feature #1878: Trigger on failure of another type such as file?
https://projects.puppetlabs.com/issues/1878

Author: Hari Sekhon
Status: Rejected
Priority: Low
Assignee: Nigel Kersten
Category: transactions
Target version: 
Affected Puppet version: 0.24.7
Keywords: 
Branch: 


I can find no mention of whether this is possible from looking at the type 
reference.

I want a specific exec to run only when another file definition fails to source 
it's file from a puppet:// server.


-- 
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.

Reply via email to