puppetdb also expose facts etc. details via api calls too, you might want
to check that out.
take a look at hiera-gpg puppet module to store hiera variables in
encrypted form, it will provide enough security on hiera/git side.
On Mon, Nov 4, 2013 at 7:49 PM, Arnaud Gomes-do-Vale
You can use splay to schedule agent run and yes, you can view agent run /
changes status in /var/log/messages.
http://docs.puppetlabs.com/references/latest/configuration.html#splay
-V
On Mon, Sep 16, 2013 at 4:27 PM, Adeel Bhatti adeelarifbha...@gmail.comwrote:
Hi,
Is it nesseccary to
Well, actually it is straight forward.
Just create a ssh_authorized_keys resource for an user for both nodes and
store the private key in .ssh/id_rsa or define Identity key file in
.ssh/config.
On Sat, Aug 3, 2013 at 7:12 AM, Mark Ruys mark.r...@gmail.com wrote:
With the risc I ask a
If you are using hiera, you can set the default value to UNSET for those
variables, it should do it.
*rabbitmq_port = hiera('**rabbitmq_port','UNSET')*
*
*
If you are using host facts, you can modify if condition like this:
*% if **@rabbitmq_port != '' and **@rabbitmq_port != 'UNSET' -%*
*
*
If you are managing sssd* package(s) via puppet, you can try this:
module.pp -
if defined(Package['sssd']) and defined(Package['sssdxx'])
{
$session_variable = sss.so
}
else
{
$session_variable = pam_ldap.so
}
template.erb -
session optional %= session_variable -%
-
On Tue,
