Okay back to the original problem. It's become a bit hard to follow.
Without code change to puppet you're stumped. But without knowing your systems
a combination of package based deployments and excluding mode or owner maybe
will get you by?
But with puppet code change, would a way of doing what you are proposing be
something like this:
file { title:
owner => name,
mode => 0755,
content => content,
notify.=> service[name],
notify_on => ['owner', 'content'],
}
Now I don't know how easy that is to code into puppet, but I think that would
sound like a useful feature to me.
Regards,
Den
On 19/06/2012, at 10:11, "Shawn" <taaj.sh...@gmail.com> wrote:
> Brutal you are.
> -yoda
> Sent via BlackBerry
> From: Jo Rhett <jrh...@netconsonance.com>
> Sender: puppet-users@googlegroups.com
> Date: Mon, 18 Jun 2012 17:07:21 -0700
> To: <puppet-users@googlegroups.com>
> ReplyTo: puppet-users@googlegroups.com
> Subject: Re: [Puppet Users] can we avoid notify/subscribe firing on a mode
> change?
>
> Right, sure. Instead of 18 lines of puppet policy that do exactly what I
> need, I should instead go create an infrastructure based around a barely
> documentation and SLOW part of puppet. Because who wants finer granularity
> for your controls, when you could implement a huge infrastructure instead?
>
> I take it you are a bit too young to have watched companies go out and
> implement Active Directory to solve a minor technical problem, aren't you?
> There is no value in implementing an infrastructure with its own requirements
> for redundancy and its own dependancies to solve something you can code in an
> hour.
>
> On Jun 18, 2012, at 4:27 PM, Eric Shamow wrote:
>> No - if it's that small and simple, the data bout which host is in which
>> should be in your source of truth, CMDB, etc - and Puppet should read that
>> data and determine which attribute or set of attributes (or resources) is
>> applied based on that.
>>
>> You can do this today with hiera and conditionals.
>>
>> --
>>
>> Eric Shamow
>> Professional Services
>> http://puppetlabs.com/
>> (c)631.871.6441
>>
>>
>>
>> --
>> 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.
>
> --
> 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.
> --
> 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.
--
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.
