How to ignore one specific change event?

Support
#1

I have one specific resource, which always changes, and which I would
like ignored by foreman…

The resource in question is a file:

file { "/etc/mcollective/facts.yaml":
ensure => file,
content => inline_template("<%= scope.to_hash.reject { |k,v| (!(
k.is_a?(String) && v.is_a?(String) ) || (k =~ /password/i)) }.to_yaml
%>"),
noop => false,
loglevel => debug,
}

It's always changing, and that is expected. As result, foreman always
showing that all my nodes had one change applied to them…
Is there any way, in foreman, or in puppet, I could cause this one
resource to never be reported on?

Thanks a lot.
Mohamed.

#2

> I have one specific resource, which always changes, and which I would
> like ignored by foreman…
>
> The resource in question is a file:
>
> file { "/etc/mcollective/facts.yaml":
> ensure => file,
> content => inline_template("<%= scope.to_hash.reject { |k,v| (!(
> k.is_a?(String) && v.is_a?(String) ) || (k =~ /password/i)) }.to_yaml
> %>"),
> noop => false,
> loglevel => debug,
> }
>
>
> It's always changing, and that is expected. As result, foreman always
> showing that all my nodes had one change applied to them…
> Is there any way, in foreman, or in puppet, I could cause this one
> resource to never be reported on?
>
> as far as it goes to foreman not afaik, you could hack around, but
it doesn't sound pretty.

maybe you could think of generating that file in another manner, (for
example link it to a local output of facter --yaml?)

Ohad

··· On Wed, Mar 30, 2011 at 10:49 PM, Mohamed Lrhazi wrote:

Thanks a lot.
Mohamed.

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

#3

I like how when generated by puppet, that facts file also includes all
variables defined in the puppet run, such as "servername", which is
the last puppetmaster the node spoke to…

Would it be hard for me to hack a "pre-filter" function into foreman's
report receiving logic?
Where in the code should I start looking, if I wanted to add such a thing?

Thanks a lot.

··· On Wed, Mar 30, 2011 at 5:04 PM, Ohad Levy wrote: > > > On Wed, Mar 30, 2011 at 10:49 PM, Mohamed Lrhazi wrote: >> >> I have one specific resource, which always changes, and which I would >> like ignored by foreman... >> >> The resource in question is a file: >> >> file { "/etc/mcollective/facts.yaml": >> ensure => file, >> content => inline_template("<%= scope.to_hash.reject { |k,v| (!( >> k.is_a?(String) && v.is_a?(String) ) || (k =~ /password/i)) }.to_yaml >> %>"), >> noop => false, >> loglevel => debug, >> } >> >> >> It's always changing, and that is expected. As result, foreman always >> showing that all my nodes had one change applied to them.... >> Is there any way, in foreman, or in puppet, I could cause this one >> resource to never be reported on? >> > as far as it goes to foreman not afaik, you could hack around, but > it doesn't sound pretty. > maybe you could think of generating that file in another manner, (for > example link it to a local output of facter --yaml?) > Ohad >> >> Thanks a lot. >> Mohamed. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To post to this group, send email to foreman-users@googlegroups.com. >> To unsubscribe from this group, send email to >> foreman-users+unsubscribe@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/foreman-users?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To post to this group, send email to foreman-users@googlegroups.com. > To unsubscribe from this group, send email to > foreman-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/foreman-users?hl=en. >