Hi,
In /etc/puppet/hieradata/users/ I have 2 yaml files.
For a node I want to merge these files and on the other node only one file.
In the /etc/puppet/enc/nodes/server1.yaml I have:
---
classes:
- ssh
parameters:
usergroups:
- group1
- group2
And on the other node only -group2.
Hello,
sorry, but I do understand your réponce:
but if I change something on the nodes/puppet-sql.alflab.net it gets
reflected into the node with the new catalog.
Mysql installed?
different commands past returns 'nil':
>> DEBUG: Fri Sep 04 20:19:04 +1000 2015: Looking up postgresql::server
Hi David.
Here is the output
[root@puppet-server puppet]# ls -rtla /etc/hiera.yaml
lrwxrwxrwx 1 root root 22 Sep 4 14:46 /etc/hiera.yaml -> /etc/puppet/hiera.yaml
[root@puppet-server puppet]#
The owner was root so I changed it as per your suggestions so now it's puppet.
But still can't
I'm trying to move over to AWS. Been installing puppet open source on
Amazon Linux AMI.
After hours of struggle, finally got passenger(ruby rack) to start.
("/var/log/httpd/error_log" been saying it can't find passenger rack to
start but I provided correct ruby path now).
But
HI,
I have set up a master with 400+ agents. My master has 2015.2. I have to
setup 4 environments and all are test environments. I've tried creating
directories named with the test environments at
/etc/puppetlabs/code/environments/test1
/etc/puppetlabs/code/environments/test2
On 2015-19-08 8:39, David Racodon wrote:
Hi John,
Thanks for your feedback. Actually, puppet-lint goes against this
recommendation because it flags quoted resource titles containing only a
variable as an issue: "string containing only a variable on line 8".
Which is a different problem,
Thank you! I opened a ticket earlier as well after posting this
(https://tickets.puppetlabs.com/browse/MCO-722) - I didn't see the two that
you posted.
(In the meantime, I'll be trying to work around by installing from source
into the 'libdir' if I can.)
On Friday, September 4, 2015 at
As Trevor mentioned above this is something you want to control externally
via cron and not puppet. I took a slightly different approach and used an
external fact which allowed be to write a fact in bash. There is no reason
why you couldn't do this in a Ruby based fact but since all the
