This is a very old thread, but I am a new puppet user and it still seems very relevant.
I am a SuSE user struggling to find a tidy way of managing repository keys, but I think the principles are the same for all distributions. As far as I can see, both yumrepo and zypprepo are of limited value because they don't provide a mechanism to import keys. I suspect most people bottle out of this by disabling the GPG checking, and that sounds to me like a bad idea. So I think the way to go is (1) new type packagerepo to supercede yumrepo and zypprepo (2) the gpgkey parameter should do something useful, i.e. import the key from the puppet server Then the administrator would install trusted keys on the Puppet server and they would be automatically distributed to clients. I may well be missing something here, so I am happy to be corrected if i am wrong Bob On Tuesday, 8 December 2009 21:02:28 UTC, Julian Simpson wrote: > > > I meant implementing a new type like aptrepo there. Actually the best > > design decision would be: rename yumrepo as packagerepo, split some of > > the code as a provider yumrepo, add new code for a provider aptrepo. But > > that isn't easy as pie and it requires ruby knowledge, apt and puppet > > internals. This is the elegant, but complex solution. Now I'm > balabbering. > > You're not blabbering. A new type in Puppet seems like the right idea to > me. > > J. > > -- > Julian Simpson > Software Build and Deployment > http://www.build-doctor.com > http://twitter.com/builddoctor > -- 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/-/qGmj6SxAicUJ. 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.
