On Jun 18, 2012, at 12:55 AM, Felix Frank wrote:
> this thread is starting to confuse me, I am no longer sure what you're
> suggesting, precisely.
> 
> a) Make it possible to nullify notifications under certain circumstances.
> b) Make it possible to ignore file owner/mode for files that exist already.
> 
> While (b) is rather tasteless to me (as is the whole "replace"
> parameter), it is certainly well in line of what's possible today, so I
> wouldn't object too much.
> (a) is a nightmare I hope you're not invested in.

Well, a in the service of b -- but as a general point, I think that every 
notify/subscribe should be tune-able as to which things changing will cause the 
action to take place.

>> I'm thinking of sites where you edit a policy and two seconds later
>> someone on a different team "kicks" the host for an entirely different
>> reason. And perhaps they should have used a tag to limit what they
>> kicked, but perhaps they forgot. Or perhaps their module depends on
>> yours so they so added your module as a tag.
> 
> This statement in itself is interesting as well. I believe that most
> sites, large or small, don't face this particular problem at all,
> because most of its incarnations are handled by manifest code control.
> If a change goes to production, it better work, otherwise whoever pushed
> to production has to answer for the breakage.

Exactly, which is why I said that the suggestions that someone edit the policy 
in advance and then send it out at the appropriate time make no sense at all.

> If you have a service that should under no circumstances be restarted
> unattended, then for crying out loud, do not make it consume resource
> notifications from puppet. That's begging for trouble.


That's not what I said. I said should not be restarted for any reason other 
than a change in the configuration file.

Not a change in the ownership for new sites.
Not a change in the mode for new sites.
etc...

-- 
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet projects.



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to