On Tuesday, March 11, 2014 7:44:58 AM UTC-4, Dirk Heinrichs wrote:
>
> Am 11.03.2014 10:17, schrieb Dirk Heinrichs:
>
> To do this, I've placed a simple text file "custom_facts.txt" into
> C:\ProgramData\PuppetLabs\facter\facts.d with content
>
> [facts]
> role = PuppetDev
>
>
> Got it to work
On 11 Mar 2014 10:21, "Dirk Heinrichs" wrote:
>
> To me it looks like facter is reading the file containing the custom
fact, while the agent does not.
Puppet uses /etc/puppet/hiera.yaml (or /etc/puppetlabs/puppet/hiera.yaml
for PE) not /etc/hiera.yaml. You could symlink them so that the hiera
com
Am 11.03.2014 10:17, schrieb Dirk Heinrichs:
> To do this, I've placed a simple text file "custom_facts.txt" into
> C:\ProgramData\PuppetLabs\facter\facts.d with content
>
> [facts]
> role = PuppetDev
Got it to work by removing the blanks:
role=PuppetDev
Bye...
Dirk
--
*Dirk Heinrichs*,
Am 11.03.2014 10:31, schrieb Craig Dunn:
> Drop the :: from your hiera.yaml, it's being taken literally as
> '::role' rather than defining scope.
That doesn't help, unfortunately. OTOH, using a predefined fact works
fine. For example, I also have a line
- "node/%{::fqdn}"
in hiera.yaml and I c
Drop the :: from your hiera.yaml, it's being taken literally as '::role'
rather than defining scope.
Regards
Craig
On Tue, Mar 11, 2014 at 9:17 AM, Dirk Heinrichs wrote:
> Hi,
>
> I'm trying to categorize our Puppet agent nodes via custom facts. To do
> this, I've placed a simple text file "c
Hi,
I'm trying to categorize our Puppet agent nodes via custom facts. To do
this, I've placed a simple text file "custom_facts.txt" into
C:\ProgramData\PuppetLabs\facter\facts.d with content
[facts]
role = PuppetDev
When I call facter on the agent node, I can see the new fact.
On the server, I'
