So I didn't have a "/etc/puppet/modules/env/lib/facter/" directory
structure of any kind.
I had a structure of "/var/els/puppet/modules/facts/files/envir.rd"
and /var/els/puppet/modules/env/lib/facter/envir.rb"
Neither of those work, however, I am just running facter. If puppet runs
facter
So I didn't have a "/etc/puppet/modules/env/lib/facter/" directory
structure of any kind.
I had a structure of "/var/els/puppet/modules/facts/files/envir.rd"
and /var/els/puppet/modules/env/lib/facter/envir.rb"
Neither of those work, however, I am just running facter. If puppet runs
facter
On 09/07/2014 04:12 AM, Matthew Monaco wrote:
> Hello,
>
> Puppet-3.6 here, although I think this has been bothering me since 3.4 or 3.5.
> (Waiting on PUP-3190 for 3.7). I have this seemingly innocuous class:
>
> -8<--
> class ldap::slapd::nsso
Hi Alex,
Not sure about the 'Not Authorized' error message, but the URI you're
using to retrieve the file seems wrong.
Based on Puppet official doc[1], the correct pattern is :
puppet:///modules/name_of_module/filename
But the one you're using is more like :
puppet:///name_of_module/path/t
On 09/07/2014 05:41 PM, omfg9899 wrote:
> I have placed this file in MANY different places as suggested and it
> never works.
Well...*what* places?
The facts.d directory is the one place where this does *not* belong.
Please try /etc/puppet/modules/env/lib/facter/envir.rb
provided that /etc/pupp
P.S. If I run "facter envir.rb" it works, it shows up in the list.. :/
J
On Sunday, September 7, 2014 10:41:28 AM UTC-5, omfg9899 wrote:
>
> I know I must be missing something stupid, but I have tried for 2 days
> now without success.
>
> I am using puppet stand alone, no master.
>
> I ne
I know I must be missing something stupid, but I have tried for 2 days
now without success.
I am using puppet stand alone, no master.
I need a simple custom fact to be created to assist in deploying the
correct configuration at build time.
I made this super simple fact..
# envir.rb
F
On 09/06/2014 11:09 PM, Spencer Krum wrote:
>
> $java_home = $java_home_var
>
> Barring that, this is the correct way to use a template:
>
> $java_home = inline_template('<%= @java_home_var %>')
Well, yes, but I got the impression that the OP has a *variable name*
stored in $java_home_var and need
Hello,
Puppet-3.6 here, although I think this has been bothering me since 3.4 or 3.5.
(Waiting on PUP-3190 for 3.7). I have this seemingly innocuous class:
-8<--
class ldap::slapd::nssov {
include ldap::slapd::rfc2307bis
# FIXM
