Hmm okay. I was trying to figure out if i should add the latest redis module to Puppetfile or the one listed in metadata.json. Latest redis module is newer then what’s asked for in metadata.json. Hope i’m making sense.

you should add the module, with a version that matches the version

Okay, thank you

🎉 erb2epp can rewrite

.each do |k,v|

to

.each |k,v| {

now!

working on prepending the variables with

$

ewoud: I’m going to update the latest PR with another set of changes as it’s not merged anyway 🙂

code is weird! because I can write a C program in any language! 😄

but at least someone can improve it after

@Yury Bushmelev and my cat can write valid perl by walking across the keyboard!

Reminds me of the eternal question, did I write valid lisp, or is the

)

key on my keyboard stuck

👋 We're starting to look into migrating (finally) from an older deprecated module ( example42 / puppet-network ) to puppet-network, and was looking through recent issues and changes, and saw that

puppet-boolean

is a required module but has been recently deprecated. It seems there are issues with setting

onboot

to

yes|no

and it always insists on setting it to

true|false

. The

puppet-boolean

module seems like it was used just for comparison of those truthy values, but is there a way to set an actual string for things like

onboot

and

hotplug

so they're

yes|no

vs

true|false

. Some of the RedHat network scripts do strict comparison on things being

no

for example, so not being able to set these properly is causing some strain while we migrate 😕

@jplindquist I recommend using systemd-networkd, everything else is painful or not properly maintained

with our puppet-systemd module, of course.

See the

puppet-systemd

module at https://forge.puppet.com/puppet/systemd?src=slack&channel=voxpupuli

Looking into that, the puppet-network one was the "recommended" one, so here I am 😛

See the

puppet-network

module at https://forge.puppet.com/puppet/network?src=slack&channel=voxpupuli

I dont recommend the network module :)

TIL

Let me look what's involved with this vs. the older network-scripts way of managing things

Parsing through it now

the network module is as old and fragile as network-scripts

systemd-networkd provides an ini format for managin network settings that works on every modern OS

and not just RHEL or just debian

Noice

here is an example, I manage my home network router and other devices with systemd-networkd and puppet-systemd: https://gitlab.com/kenyon/puppet/-/blob/9361e341260fc1397b5c89e9855d5f0e928b4a6b/data/nodes/router.kenyonralph.com.yaml#L63

and since you have systemd anyway, no matter if you like it or not, you can just use it

It is a bigger move than just the module change though, changing the whole "what configures the network" mechanism. Worth pointing out

This will be a bigger change than what I was originally planning for

We are good at introducing changes

here is the common config for machines with Ethernet and DHCP https://gitlab.com/kenyon/puppet/-/blob/9361e341260fc1397b5c89e9855d5f0e928b4a6b/data/kernel/Linux.yaml#L132