This message was deleted.

This message was deleted.

Hi all! I'm implementing dnf module support in Puppet and, after a long talk in #C0W1Y5VL0, there seems to be 3 possible homes for the code: 1. package resource dnfmodule provider. It already has some dnf module support, but focused in the packages, not modules (since it's 'package' resource anyway). I could just extend dnfmodule provider functionality, but making package resource manage dnf modules (as opposed to packages only) always sounds abusive to me. 2. yum Forge module. Since dnf is the "new yum", yum module supporting dnf stuff makes sense to me. 3. A new dnf module. Probably overkill, but could be an option if there's any intention inside Puppet of splitting yum and dnf. Could you pls help me decide the way to go? The implementation itself is almost done (not that hard indeed) - I just want to publish that in the right place. Thanks!

This message was deleted.

on puppet 4, the certregen module appears to not be usable

any suggestions for regenerating the CA (with the same key)

Upgrade to Puppet 7 or 8. You're a decade out of date.

not helpful

The overwhelming majority of work that has been done to automate regenerating the CA certificate started in the Puppet 6 timeframe.

This message was deleted.

This message was deleted.

This message was deleted.

I don't recommend that, but since it's Puppet 4 anyways...

if it's already expired, you'll have to regenerate the cert and reconnect all the devices

This message was deleted.

This message was deleted.

check #C0W1Y5VL0

Anyone have ideas managing mounts with windows clients? Specifically Samba and NFS network mounts.

windows can do nfs mounts? now I lived to see everything 🤯

former colleague of mine wrote karmafeast/windows_smb

See the

karmafeast-windows_smb

module at https://forge.puppet.com/karmafeast/windows_smb?src=slack&channel=puppet

This message was deleted.

My r10k failed this morning too. I bet forge or github had issues

the more you know Content and Tooling is about to start up in #CFD8Z9A4T

hello again 🙂 I'm fighting again with some crap code written in puppet 3 and I'm unable to get it to work on 7.

code

  $application_version      = $::application::application_version
  $application_core_version = lookup("application::application_${application_version}_package_version", {'default_value' => '1.0.1.1-1101'})
  $application_libs_version = lookup("application::application_${application_version}_libs_package_version", {'default_value' => '1.0.1-1'})

yaml

application::application_version: '2.0.2.2'
application::application_2.0.2.2_package_version: 2.0.2.2-2222
application::application_2.0.2.2_libs_package_version: 2.0.2-2

The issue is that the lookup in hiera doesn't work and always gives me the default values for $application_core_version and $application_libs_version I've added a notify to check the variables for application_version and that returns the correct value. Any ideas??

Drop the leading :: in the key in your call to lookup - does that help?

no it doesn't sorry, that's a mistake, in my copy

All periods in the key must be “escaped” since a period is taken as drill down into the data.

If the key is “a.1.2”, use the string “a’1.2’” as inout to lookup.

Or ‘a”1.2”’