atomically. What I mean is, suppose some class required another class...
an application requires a file to exist. You can actually make that file
first on the target host and then install or change the application.
I'm trying to deal with a host that only permits changes in batches.
Effectively all the changes are put into a "window" and then the window is
committed. Something on the backend (separate from puppet) in the host
handles the ordering of the individual elements.
What is the best way of dealing with this in Puppet? We don't want to
expose the final "commit" to the person building manifests for hosts.. we
want to reuse those abstractions on other platforms that don't use a change
Obviously, we're going to build a provider. We can't embed a commit into
every atomic element (committing a window, no matter how big or small takes
too long), we just want to ensure that whenever configuration state is
modified for this host, all changes are put into the window and then a
single final commit is executed..
I'm probably not the first to ask, but I spent some hours looking around in
books, internet, etc... didn't really grok how to do this. If I missed
something, please provide a pointer or link...
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/Zuqkz_u-T-cJ.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to firstname.lastname@example.org.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.