On Monday, December 3, 2012 2:32:15 PM UTC-5, j4m3s wrote: > > Though we have lots of automated testing we still rely on the human touch > for checking UI look and feel, and doing exploratory testing (in the pre > production environment). Once it has passed this step the human can > approve it for production deployment by updating the version number in > hiera. I guess we could have a button on a web screen or something to make > it easier to promote it, but editing hiera directly is easy enough. If you > have a central change management system, it could update hiera - but you'll > still want it approved for promotion by a human won't you, to take into > account live service stability/ load, etc? >
Do you use hiera to define not only the versions but also which applications should be on which environments? How do you introduced application version 1.0 to dev for the first time? -- 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/-/5n3FDDQjhlYJ. 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.
