Thanks.
While I see that Ansible is a nice tool, the clientless access requiring a
login has a fatal flaw when compared to puppet.
More than once we have had a PAM, SSHD or similar setup get corrupted over
dozens, if not all, systems. We were able to fix in Puppet and get the
corrections pushed o
Am Donnerstag, 15. September 2016 14:53:57 UTC+2 schrieb HPUX_PUPPET:
>
> ...
>
> This post was mainly about seeing if Puppet / Factor had been tweaked over
> the years to pull lists of installed RPMs given Red Hat Satellite 6 using
> Puppet as part of their software management and server build
I don't think you'll see that added as a core fact because it would still
have a relatively narrow appeal. Due to the partnership between RH/Puppet,
there may be a Satellite mod that includes such a custom fact. If you do
something like that yourself, I would keep an eye on
https://tickets.puppetla
I only wish it was that simple and thus the problem i had been facing.
The 3rd party package requires hands-on steps to get installed, but the
package itself isn't the issue. It is that it puts 2-5 lines at the head of
the PAM module conf files (system-auth, password-auth, common-auth, ...).
I
Are there cases where a node might not have the package, ever? Or do you
just want to make sure it's done in the right order? If you did this:
package{'some-pam-package':
ensure => present,
}
...and the package was already installed, nothing would happen. However you
could then leverage t
Thanks Rob!
I am sort of "starting fresh" so I have a lot of latitude here. The way it
was done before was shoddy and required a lot of files, so I am trying to
reduce them.
I will go back to investigating a custom fact. I have used them in the
past, but the problem was more related to needi
I wouldn't be that shy of custom facts in Puppet 3/4 (don't know if you are
stair stepping or starting fresh), they mostly "just work". Throw them in a
module and poof, agents get them on the next run, and they're processed
before the catalog compilation of that run so they take effect immediately.
I am moving from Puppet 0.25 to Puppet 4. In doing so I am re-writing a
lot of the modules to work better than what I inherited.
So my current issue I am trying to figure out is how to update PAM
variables based on what external 3rd party authentication package we have
installed on that serve
