Hi, For deployment we do not usually use puppet. The deployment we do with are puppet are for stable in house packages. This is then done by releasing a new version in our package environment and utilizing ensure => latest for the package type.
But for frequent deployment methods I would personally look towards other means of deployment. We are currently utilizing the python fabric library for deployments. Jos On Friday, March 2, 2012 10:42:28 AM UTC+1, Thomas Rasmussen wrote: > > Hi > > I'm in the process of looking for a way to have developers deploying > on their test systems without intervention of sysadmins, to solve this > i'd like to use Puppet (either the OSS version or Enterprise, > whichever solves the problem). > > I can manage to only grant access to certain systems and limit the > ability to execute puppetd --test, however, the developers would like > to create a new version of the application and then this should be put > into place instead of the old version, but I can't seem to find a > solution to this. > > I was thinking somewhat on the option to issue a command like this: > puppetd --test --my-app-version 3.2.1 > > And then the puppet manifests will use the my-app-version variable to > fetch and deploy this specific version. I know that the manifests > should be developed with care, which is also the idea. > > Or what solutions do people use in case where developers should have > access to deploy, but not have access to the puppetmaster server? > > hope that this can be done. > > Regards > Thomas -- 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/-/MA3s32mKkTAJ. 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.
