mhm we talked about that in the past, but I dont remember it

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

After a small break in module release announcements with conferences, we are now reaching the end of Puppet 8 module updates with only the Kubernetes module awaiting an update. Supported modules released: puppetlabs-vcsrepo (6.0.1) puppetlabs-java_ks (5.0.0) puppetlabs-concat (8.0.1) puppetlabs-postgresql (9.0.3) puppetlabs-docker (7.0.0) puppetlabs-postgresql (9.0.2) puppetlabs-stdlib (9.0.0) puppetlabs-powershell (6.0.0) puppetlabs-apache (10.0.0) puppetlabs-reboot (5.0.0) puppetlabs-sqlserver (4.0.0) puppetlabs-puppet_conf (2.0.0) puppetlabs-influxdb (2.1.0) puppetlabs-kubernetes (7.1.1)

See the

puppetlabs-vcsrepo

module at https://forge.puppet.com/puppetlabs/vcsrepo?src=slack&channel=puppet

This message was deleted.

This message was deleted.

IIRC, the Foreman modules are regularly recommended for those

there's the official puppetlabs-puppetdb module, I know there is an official puppet agent module, but I don't particularly like it, so I just wrote a lightweight profile to do ini configuration where needed... for the puppet server, that I do see people suggest the foreman's module for, and I wish I had looked more into it when I was building out my setup

See the

puppetlabs-puppetdb

module at https://forge.puppet.com/puppetlabs/puppetdb?src=slack&channel=puppet

Without having to sign up for someone to contact me, what kind of yearly cost would we be looking at for around 4500 hosts on puppet enterprise?

I'd ask that in #C19V5U41Z

thanks, didn't even know that exists

This message was deleted.

At the end of the day, it’s just a design pattern, and it’s up to you. It’ll just be incumbent on you and those who work with/for you to keep it straight in your heads when reading Puppet materials. Roles/Profiles have been around quite some time now, and you’re inserting a “translation layer”. Also keep in the back of your head the “beer truck principle”. If you walk out the door and get hit by a beer truck, can anyone sufficiently knowledgeable of Puppet walk in behind you, pick up your environment, and keep moving without too much trouble.

This message was deleted.

😎

I know this as a “bus factor” 🤔

Not that many buses out here in my neighborhood

Anyone in the Portland area is invited to our PlatformCon watch party on June 8. Hit me up for details or rsvp here. https://forms.gle/ddC2aEfiryJsz7xSA

Yeah I always found the job security principle just meant nobody else would work on it and you would have to carry it alone.....

This message was deleted.

This message was deleted.

This message was deleted.

beaker 🧑‍🏫PE Console is about to start up in #CFD8Z9A4T

This message was deleted.

Just a reminder, anyone in the Portland area is invited to our PlatformCon watch party on June 8. Hit me up for details or rsvp here. https://forms.gle/ddC2aEfiryJsz7xSA

Hi all, I’m wanting to create a Symlink “latest” (which links to the top level directory of an extracted TGZ). It seems to work, but I have an ordering problem. For the file resource, I’ve tried using a require (i.e. dependency) on the Archive resource, but what I’m finding is that Puppet tries to create the symlink before the archive has actually been extracted. My code is:

archive { "/tmp/dspace-$dspace_version.tar.gz":
      source       => "<https://github.com/DSpace/DSpace/archive/refs/tags/dspace-$dspace_version.tar.gz>",
      extract      => true,
      extract_path => "$dspace_src",
      cleanup      => true,
      user         => 'tomcat',
      group        => 'tomcat',
      require      => File["$dspace_src"],
    }

    file { "$dspace_src/latest":
      ensure  => 'link',
      target  => "$dspace_src/$dspace_src_top_level_dir",
      require => Archive["/tmp/dspace-$dspace_version.tar.gz"],
    }