On Monday, December 3, 2012 11:34:53 AM UTC-5, Brendan O'Bra wrote: > > " But what these solutions have in common is that an individual at some > point in time has to make some change to the puppet system." > > Please elaborate - > Do you mean that someone has to "tell" Puppet about what versions to use? > My ultimate solution will be emitting a manifest containg the names and > versions that go into a "release" as part of our CI/release activities that > is used to "tell" Puppet what a "platform release" consisiste >
Exactly. In your case that 'someone' is the person doing the CI/release activities and the update to puppet is done by generating the manifest as part of the workflow. Evaluating this problem for the first time, there seems to be lots of potential solutions for generating the manifest with updated application versions or new applications altogether. Best practices for process release integration may not be fully established yet and everyone is doing their own thing based on what works for them. -- 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/-/0aIusLOydfgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
