easy enough, includes auto remediation.

coupled with choria you get some nice utilities like triggering fleet wide checks - say right after a maintainance event trigger a big set of checks - live view dashboards of events, historical archives of statusses, cli tooling to view a node status and the ability to pause a check, all checks, some nodes etc during maintenance windows

little stateless view of most recent states of some node

little terminal based scrolling dashboard for your environment. And all with APIs to code against for automating the aspects related to running checks and when

and each check published for analysis in cloudevents.io format for routing into other systems

and if you had crazy needs - i run this on 100s of k of nodes atm.

Nah. 100s tops 🙂 I have very boring requirements, so I’m hoping for a very boring solution!

This message was deleted.

ah sorry yeah so in general we will need to work out how we are taking the former PDK replacement work and putting it into current tools

I need any help someone can give me setting up multifactor authentication into the Puppet Web Console. One big obstacle is that we do not have access to a SAML provider due to having an internal network. I am also open to using tokens to restrict if someone can login but at the moment when someone enter their password it creates a new token and lets them in. Is it possible to restrict this to admin created tokens only? I cannot find where Puppet covers this topic.

This message was deleted.

I'm looking for advice/opinions on how to handled a configuration file in a module I'm about to update. I'm planning on making a pull request to saz/puppet-limits and I'm going to make changes so that the module will manage /etc/security/limits.conf on RHEL and variants. The limits.conf files for RHEL7 and RHEL8 are identical. Should I have one file and then a symlink to the first file or should I have two identical files in ./templates?

r10k manually (with the command we talked about last week) works on puppet7.

Don't use a symlink within the Puppet module itself. Best bet is to use the same template for both RHEL7 and RHEL8. If in the future you find that there are differences, you handle that by feeding different data to the template's inputs.

RHEL9 has a somewhat different limits.conf file. Would I be correct in assuming that I should not try to reproduce rhel7, rhel8 and rhel9 limits.conf with a single template?

...and I should use a different limits.conf template for rhel9? The stock limits.conf file is just a bunch of commented out examples.

I've got a setup with dual MTA's managing my email an edge network that just accepts domains - does a load of scanning then forward to an internal MTA if the scans are clean. The trap is, the internal MTA is managed via a mariadb or postgres database to hold all the virtual maps etc, I don't want the edge MTA to read the database directly, as it defeats the object of the edge MTA. I wondered if I could have a puppet module connect to the database, run a query and format the output into a template, that the edge MTA could pickup, so if I add a mailbox to the internal mail setup, the edge MTA is aware it's a legit domain/mailbox and will process it rather than drop it

how could I approach this with puppet, I've never done this sort of thing with puppet

Puppetboard question - I'm failing to get this working on a freebsd 13.1 OS due to this unavailable package. The package actually IS available, and is already installed, but it's 'py39-pip'...not py3-pip. I've grepped thru every file on my system and cannot figure out a work around. Anyone? Beuller? If anyone can even just point me to a forum/wiki/IRC, anything, much appreciated! Thanks!

@Ken I use this in my python profile:

3   class { 'python':
  4     version => '39',
  5     dev     => 'present',
  6   }

Maybe the default value need tweaking?

yes. I quite liked Sensu when I replaced Nagios. It can be extended with lot of handlers. You can write handler yourself (if you ever need it). The Puppet module is quite good (it's maintained by Garret). I'd like to hear other people's opinion about it.

This message was deleted.

This message was deleted.

same applies to foreman but that's another story

I have opened a bug on debian but that went closed wontfix

Hello everyone ! Does someone know why with this code :

apt::source { 'aptly':
    location => '<http://repo.aptly.info>',
    release  => 'squeeze',
    repos    => 'main',
    key      => { 'id' => 'E25D52818DF39C4A8D24668DEE727D4449467F0E' },
  }

This lane is displayed EVERYTIME I run puppet ?

Notice: /Stage[main]/aptly::Install/Apt::Source[aptly]/Apt::Key[Add key: E25D52818DF39C4A8D24668DEE727D4449467F0E from Apt::Source aptly]/Apt_key[Add key: E25D52818DF39C4A8D24668DEE727D4449467F0E from Apt::Source aptly]/ensure: created (corrective)

message has been deleted

This message was deleted.

indeed Content and Tooling is about to start up in #CFD8Z9A4T