Prevent LWRP from notifying?


#1

Currently I am using the python cookbook (authored by opscode). When
installing a pip with it, it always sends a notification even if it noops
because the pip is installed already. I was wondering if it is possible for an
LWRP to not send a notification when it NOOPS.

I dug into the resource code a bit and I noticed that most full fledged
providers (like the template resource) use updated_by_last_action. Is this
what causes the notifications or not?

Any input would be lovely as there are a bunch of processes I’d love to restart
only after a pip has been installed.


#2

Brian,

It appears that the pip provider in opscode-cookbooks/python will always
mark the resource as updated-by-last-action, regardless of the result of
whatever it does under the hood.

Take this bit:

It looks like the status variable will always have a truthy value and pass
an “if” test because it will always have an instance of Mixlib::ShellOut.
The only values that are falsy and fail an “if” test are false and nil;
all other values are truthy.

Cheers,
Jay

On Mon, Jul 9, 2012 at 10:32 AM, brian.bianco@gmail.com wrote:

Currently I am using the python cookbook (authored by opscode). When
installing a pip with it, it always sends a notification even if it noops
because the pip is installed already. I was wondering if it is possible
for an
LWRP to not send a notification when it NOOPS.

I dug into the resource code a bit and I noticed that most full fledged
providers (like the template resource) use updated_by_last_action. Is this
what causes the notifications or not?

Any input would be lovely as there are a bunch of processes I’d love to
restart
only after a pip has been installed.