If you can't find a prebuilt module to do this, it would be super easy
for you to write your own. Report processors are pretty straight-forward.
If you started by copying the tagmail module, then ripped out the SMTP
bits and added in write-to-file bits, you'd have to write... probably
less th
I searched through all the reports processors on puppet forge but did not
find one that writes tagmail like reports to file...
Can any one point us to something like this?
Regards,
Daniel
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To u
Huh, looks like you're right-- the latest deb
(puppetserver_2.6.0-1puppetlabs1_all.deb) doesn't contain the file, but
dpkg -L still shows it as part of the package. Maybe this is a bug in dpkg?
Thanks for testing that.
On Tuesday, September 13, 2016 at 3:05:29 PM UTC-6, Joe Pinsonault wrote:
>
It's a known bug, the best option i have come with is to create a module to
manage the base repositories using augeas instead of yumrepo.
On Monday, September 12, 2016 at 6:48:15 PM UTC+3, Jonathan Gazeley wrote:
>
> Hi folks,
>
> I'm working on a manifest that manages the stock yum.repos.d defi
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
