Prevent LWRP from notifying?

Brian_Bianco · July 9, 2012, 2:32pm

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.

Jay_Feldblum · July 9, 2012, 4:07pm

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:

github.com

poise/python/blob/e9e4f24d9203446e072f0d15e3d3330310994676/providers/pip.rb#L46-49


      
            end
          
            # Set the timeout (units in seconds)
            timeout = 900
            if @new_resource.timeout
              timeout = @new_resource.timeout
            end
          
            if install_version
              Chef::Log.info("Installing #{@new_resource} version #{install_version}")
              status = install_package(@new_resource.package_name, install_version, timeout)
              if status
                @new_resource.updated_by_last_action(true)
              end
            end
          end
          
          action :upgrade do
            # Set the timeout (units in seconds)
            timeout = 900
            if @new_resource.timeout

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.

Topic		Replies	Views
Missing Notification from LWRP Chef Infra (archive)	5	589	February 11, 2012
Chef LWRP and new_resource.updated_by_last_action and use_inline_resources Chef Infra (archive)	1	1399	July 1, 2015
LWRP + notification Chef Infra (archive)	3	409	August 19, 2013
How to suppress notifications in LWRP Chef Infra (archive)	9	393	April 23, 2013
Idempotent lwrp behaviour Chef Infra (archive)	3	340	September 10, 2014

Prevent LWRP from notifying?

Related topics