Comment 20 for bug 1485505

reexecute_on: [deploy_changes] doesn't reflect the use case and adds even more burden to plugin developers. If I'm a plugin developer, I need to override the following base tasks if I want to update rabbitmq and memcache nodes list:
${plugin}_hiera_config
hiera
globals (actually this is already in master)
cluster
memcache

But then you will re-execute these tasks on controller as well... and again on add/remove of controllers, cinder nodes, compute nodes... etc. I want to narrow the scope of repeating puppet just for the case of adding/removing a node with my plugin's role.

The fact remains that a parameter "update_required" exists and has a very clear criteria, but does not work as expected.