Add an optional "content" parameter to the freeradius::cert resource.

This allows the user to pass in raw content rather than just
a direct file resource. Great for use cases where people don't
store private keys in raw files in their repo, but use some alternative
method to get them.

README.md

@@ -148,6 +148,13 @@ freeradius::cert { 'mycert.pem':
 }
 ```
 
+```puppet
+freeradius::cert { 'mycert.pem':
+  content => '<your key/cert content here>',
+  type    => 'key',
+}
+```
+
 ##### `type`
 
 Set file permissions on the installed certificate differently depending on whether this is a private key or a public certificate. Note that the default is to treat the file as a private key and remove world-readable privileges. Allowable values: `cert`, `key`. Default: `key`.

manifests/cert.pp

 # Install FreeRADIUS certificates
 define freeradius::cert (
-  $source,
+  $source = undef,
+  $content = undef,
   $type = 'key',
   $ensure = present,
 ) {
@@ -21,6 +22,7 @@ define freeradius::cert (
     owner    => 'root',
     group    => $fr_group,
     source   => $source,
+    content  => $content,
     require  => [File["${fr_basepath}/certs"], Package[$fr_package], Group[$fr_group]],
     notify   => Service[$fr_service],
   }