Hi,

I'm wondering if there's an established way on how to write and improve 
modules with potentially system-breaking or incompatible changes. One 
example are changes in the filesystem layout, or simply the change of an OS 
user's homedir (usermod fails because of running processes).

Of course, Puppet isn't at fault here, but the question is: How do you 
write a module to support this? It's not always possible to just bootstrap 
the server again (=> potential downtime), or breaking Puppet runs until 
there's time to manually prepare the server for changes.

We could use multiple environments and Puppetfile's (r10k). On the other 
hand, this means that there are a lot of environments to manage (deploy 
module updates, ...).

Any other angles (or posts somewhere) on this?

Sven

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/0d485460-fefe-43df-b060-cd769818a643%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to