Re: [Puppet Users] Custom fact ( complete fail )

2014-09-08 Thread omfg9899
I didn't want to leave this unanswered.. In the end, I had to create a "script" using the "files" function inside cloud formation. In the "script" I set the value "FACTERLIB=/var/els/puppet/modules/facts/files" and in that same script executed my puppet apply command and it worked. Amaz

Re: [Puppet Users] Custom fact ( complete fail )

2014-09-08 Thread omfg9899
I may not have been clear.. We don't "currently" use a puppet master, although we are currently evaluating this, among other options moving forward. The mess I was left with appears to have absolutely minimal configuration as to just get to point B as quickly as possible. So when these i

Re: [Puppet Users] Custom fact ( complete fail )

2014-09-08 Thread Garrett Honeycutt
On 9/7/14 11:41 AM, 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 need a simple custom fact to be created to assist in deploying the > correct configuration at build time. >

Re: [Puppet Users] Custom fact ( complete fail )

2014-09-08 Thread Felix Frank
On 09/08/2014 05:29 PM, omfg9899 wrote: > puppet apply --configprint modulepath > /etc/puppet/modules:/usr/share/puppet/modules > > puppet apply --configprint environmentpath > invalid parameter: environmentpath > > > > I inherited this, and am thinking more and more that it wasn't > implement

Re: [Puppet Users] Custom fact ( complete fail )

2014-09-08 Thread omfg9899
puppet apply --configprint modulepath /etc/puppet/modules:/usr/share/puppet/modules puppet apply --configprint environmentpath invalid parameter: environmentpath I inherited this, and am thinking more and more that it wasn't implemented anywhere close to best practices. So the environmentp

Re: [Puppet Users] Custom fact ( complete fail )

2014-09-08 Thread Felix Frank
As I mentioned, you *modulepath* is key here. What is the output of puppet apply --configprint modulepath puppet apply --configprint environmentpath Also, what version of Puppet is this? On 09/08/2014 06:19 AM, omfg9899 wrote: > So I didn't have a "/etc/puppet/modules/env/lib/facter/" directo

Re: [Puppet Users] Custom fact ( complete fail )

2014-09-07 Thread omfg9899
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

Re: [Puppet Users] Custom fact ( complete fail )

2014-09-07 Thread omfg9899
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

Re: [Puppet Users] Custom fact ( complete fail )

2014-09-07 Thread Felix Frank
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

[Puppet Users] Custom fact ( complete fail )

2014-09-07 Thread omfg9899
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