Re: [Puppet Users] inheriting ssh_authorized_key

Thanks Pete! I owe you a beer. Using defines this way works much better. And, for my issue with adding options, it's just a matter of passing in the options to the define, then using: ssh_keys::bob{"repo": options => "command=\"svnserve -t --tunnel-user=bob\""} Often it's hard for me to get in

Re: [Puppet Users] disable ssl

No I am not using environments with this setup, curious on how that would make a difference if the module base is identical for all of my production hosts. By using a subject altname on the cert would that allow for a distributed certificate for all my hosts in that specific environment. Since ea

Re: [Puppet Users] config settings for environments

On Wed, 10 Mar 2010, Rob McBroom wrote: > Hello. The documentation on using multiple environments says there are > only a couple of settings that make sense per-environment (modulepath, > templatedir, manifest) but it=??s not clear to me whether or not those > are the only ones supported. I believ

Re: [Puppet Users] disable ssl

On Sat, Mar 13, 2010 at 8:43 AM, Christopher Johnston wrote: > Sorry for the late response.  That feature looks attractive, but not > feasible at this state.  I am still running .24 version of puppet which is > working great (although performance could be slightly better!) and I wasn't > looking t

Re: [Puppet Users] disable ssl

Sorry for the late response. That feature looks attractive, but not feasible at this state. I am still running .24 version of puppet which is working great (although performance could be slightly better!) and I wasn't looking to do an upgrade to .25 for at least a month or two as bugs iron out.

Re: [Puppet Users] inheriting ssh_authorized_key

Correction: "seems to work as expected" :) overriding name gets it to the "repo" user, but does not keep in other places. Looks like I'm back to using variables. Thanks for the tip. what you can do is create a define per ssh key and then for example use $name of this define to build a title

Re: [Puppet Users] inheriting ssh_authorized_key

Correction: "seems to work as expected" :) overriding name gets it to the "repo" user, but does not keep in other places. Looks like I'm back to using variables. Thanks for the tip. --Bob -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To pos

Re: [Puppet Users] Re: Puppet 100% CPU usage

Since this is an "always run", why not just puppet a similar script into cron.hourly and lighten puppets involvement? On Sat, Mar 13, 2010 at 5:32 AM, Alan Barrett wrote: > On Fri, 12 Mar 2010, DieterVDW wrote: > > On Mar 12, 11:21 am, Patrick wrote: > > Those files are downloaded and installed

Re: [Puppet Users] inheriting ssh_authorized_key

Alan, You just reminded me that the name has to be unique. It turns out it will work when inherited, but you have to override the name as well. This works as expected: class repobob inherits ssh_keys::all::bob { Ssh_authorized_key[bob] { user=> "repo", na

Re: [Puppet Users] Re: Puppet 100% CPU usage

On Fri, 12 Mar 2010, DieterVDW wrote: > On Mar 12, 11:21 am, Patrick wrote: > Those files are downloaded and installed using apt, I just want puppet > to make sure they are owned by a certain user and group. > That's the only thing puppet needs to do. As a workaround, instead of a recursive file

Re: [Puppet Users] inheriting ssh_authorized_key

On Fri, 12 Mar 2010, Bob Belnap wrote: > I'm trying to reuse an ssh_authorized_key, but I'm having some problems. If you want to use the same key in different ways (e.g. sometimes with and sometimes without options => "command=...") then you have to use separate ssh_authorized_key resources, wit

Re: [Puppet Users] disable ssl

On Fri, 12 Mar 2010, Christopher Johnston wrote: > Reason I am asking is I am having a bunch of SSL issues in production right > now, I need to disable SSL until I get things fixed. As a workaround, perhaps you could use the standalone compile/apply feature (new in 0.25); see