Thanks for the response. I'm pretty sure I tried /etc/faster/facts.d; but, I'll
confirm that.
Thanks again.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to p
All the custom facts here in /etc/facter/facts.d have worked just fine across
the facter 2.4.4 -> facter 3.1.6 upgrade.
https://docs.puppet.com/facter/3.1/custom_facts.html
On Fri, May 27, 2016 at 12:28:50PM -0700, dkoleary wrote:
>Hey;
>I'm drafing some custom facts that I would like to
Hey;
I'm drafing some custom facts that I would like to have available to
everyone even outside of puppet. The facts themselves work just fine for
root and will work for normal users if I specify the --external-dir option:
$ sudo facter env
tst
$ facter --e
On Fri, May 27, 2016 at 6:51 AM, Gareth Rushgrove
wrote:
>
> There are lots of hints and tips in this white paper.
>
>
> https://puppet.com/blog/making-life-puppet-and-aws-or-other-cloud-services-easier
>
> In particular it covers using the policy based autosigning and trusted
> facts to secure d
IME you definitely won't have issues with 3.7.2 agents talking to a 3.8.5
master.
When you are ready to move to puppet 4, however, the upgrade docs say that
the agents should all hit 3.8 before you upgrade the master to 4.latest.
However, I skipped that step in my upgrade and 3.7.x agents talked f
On 26 May 2016 at 22:11, Martin Langhoff wrote:
> Hi Puppeteers,
>
> folks are mapping "role" from EC2 tags or userdata into a `case`
> statement in site.pp to choose a pre-built configuration.
>
> I wonder whether there is a way to bring in a listing of classes, as
> can be done with hiera (`hier
Hi, background here is that I want to use both Master and agents from the
Debian repo. The Master runs on Jessie (3.8.5 from the backports), and some
agents still on wheezy (3.7.2 from the backports).
This is not a new install, but rather an intermediate upgrade to the last
Puppet 3 version, bef
