This message was deleted.

This message was deleted.

can someone validate this will work? I primarily want to make sure the package names are correct.. imagemagick (main package) and libmagick++-dev (its library package)

class imagemagick {
  package { 'imagemagick':
    ensure => installed,
  }
  package { 'libmagick++-dev':
    ensure => installed,
  }
}

so, package names are dependent on OS

if you know those are the names of the packages for your os, that will work

thanks @Lumiere

I can't figure out what is the suggested replacement for

binford2k-node_encrypt

(since I'm seeing a deprecation notice on it). Any ideas? Thanks in advance.

See the

binford2k-node_encrypt

module at https://forge.puppet.com/binford2k/node_encrypt?src=slack&channel=puppet

This message was deleted.

we need some redirection support on Forge.. when a module author can specify that this module was transferred to another author/group

I think there's a need for both "I've handed this to another group" and an official "we've taken over this" for vox and puppetlabs

if vox or puppetlabs fork something, they should be able to put a note on it

I definitely vote for “I’ve handed this to another group” but not sure about “we’ve taken this over”.. I’d prefer maybe “deprecated” badge instead.. or “see also/similar modules” around

mostly because I don’t like to create exceptions 🙂

if module is not updated to support current set of puppet versions then it should have some special badge to see it’s outdated

I get that, but from a community perspective, having extremely limited administrative redirects I think makes a lot of sense

This message was deleted.

@binford2k ^

it’d be nice to talk about on the Forge #CFD8Z9A4T 🙂

both puppetlabs and voxpupuli have really high standards for a migration like that

yep :)

and to even improve the vox pupuli experience we are currently upgrading our CI to make it even faster #FasterTimeToMarket

now that everybody is excited about it: you can help us to improve our CI by sponsoring us on github or open collective: https://github.com/voxpupuli & https://opencollective.com/vox-pupuli

I contribute all my winnings from Puppet drawings 🙂

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

What should I check when I have 2 servers that are in the same environment and have the same roles associated to them and one of the servers deploys with changes correctly, but the other server deploys (without error), but is not applying the changes?

what's different in the logs?

It literally appears like it doesn't have the same config.

some basic advice please, I'm looking to use either the package or file resource to deploy a package or file resource, I'm trying to work out the most efficient/cleanest way to deploy a different package name depending on either the OS family or OS Family + version, fact, I've got a few usecase for this so I'd like to do it nice and clean, but the basic premise is something like if OS Family is RedHat ensure dnf-utils is installed, if OS Family is RedHat and Version is less than 8 make sure yum-utils is installed

I've found numerous ways to do this, but some real world advice on how to do this simply and efficiently would be appreciated