Thanks for your answer Evan.
For these applications, we need to have a very good control. So we'll never update them via local update utility nor use an ensure => latest We always use ensure => x.y.z We also need to be able to do rollback, so it's simpler to remove everything from say, version 1-3-2, and then apply version 1-3-1 I understand that our needs are specific, but there is something that surprise me with Puppet : if you don't explicitly remove something that was deployed previously with Puppet, then it stays For example, say you have a mount point A that you manage with Puppet For some reason, you need to change this mount point, now call it B. We could expect that if your manifest first contains A, then contains B, your intent is to remove A and creates B Puppet will just create B and leave A. It forces you to do it in two steps, first remove B, then apply and second add A then apply Any reasons why Puppet forces to explicitely remove everything that it previously installed (and that is known, thanks to localconfig.yaml file on nodes) ? nicolas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
