It's just an example of a case which is not solved by puppet language currently as far as I can tell. To solve this type of collisions "require-notify" relationship needs to be established, i.e. ability to notify refreshonly exec, for example, before changing user's attributes.
Another good example when this is necessary - lets say a service is depending on an NFS file system and you need to change a mount point. Again, mount will fail if service is running, since it won't be able unmount old one. For such a routine configuration change should be a more elegant solution than 'don't hold it this way'. Thanks, Vadym -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/5543bdb3-e9c4-44df-b357-e13f87b1d22d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
