rename stunnel::client to be stunnel::service to be less confusing (a
authorMicah Anderson <micah@riseup.net>
Fri, 2 Oct 2009 23:25:51 +0000 (19:25 -0400)
committerMicah Anderson <micah@riseup.net>
Fri, 2 Oct 2009 23:25:51 +0000 (19:25 -0400)
service can be a client in stunnel, and a service can act in server
mode, which would be confusing if it was called stunnel::client)

manifests/init.pp
templates/service.conf.erb [moved from templates/client.conf.erb with 100% similarity]

index ac060ba..7fd770d 100644 (file)
@@ -24,7 +24,7 @@ class stunnel {
     default: { include stunnel::default }
   }
 
-  define client ( $ensure = present, $accept = false, $capath = false,
+  define service ( $ensure = present, $accept = false, $capath = false,
                   $cafile = false, $cert = false, $chroot = false,
                   $ciphers = false, $client = false, $compress =
                   false, $connect = false, $crlpath = false, $crlfile
@@ -51,7 +51,7 @@ class stunnel {
                     
     file { "/etc/stunnel/${name}.conf":
       ensure => $ensure,
-      content => template('stunnel/client.conf.erb'), 
+      content => template('stunnel/service.conf.erb'), 
       owner => root, group => 0, mode => 0600,
       require => File["/etc/stunnel"],
       notify => Service[stunnel];