Puppet Community

See the `puppet-wireguard` module at <https://forge.puppet.com/puppet/wireguard?src=slack&amp;channel=voxpupuli>

anarcat: yes this is right, currently it does not reload on change

This is awesome! Let me try to find some time soon to give it a spin. I've lost a great many hours over the years trying to stub out Facter calls properly to test various Facts. I'll see if I can find one of the trickier modules I've got and try it there. Might not be this week though.

Spritzgebaeck: it seems to me that it should, any reason why it isn't so?

bastelfreak: does the systemd backend do the reload?

anarcat: at the time i built it, i didn't need it and didn't saw why it's needed. but if you need this, it should be an easy fix

<https://github.com/voxpupuli/puppet-unattended_upgrades/issues/221> this is the second useless comment from this user - I'm tempted to block for spam

ewoud:  this user joined GH 2 days ago, perhaps he does not know some rules. I prefer to warn before.

i added a comment to give some informations

Daneel: you have more patience than I do today ;)

I wondered if it could have been accidental, but twice seems odd.

that's why I said "second useless comment"

There have been times I've not noticed that my term didn't have focus and I've send random shortcut keys to a github window.

They're following a terminal emulator org, so _maybe_ there is some testing that's gone a bit wonky??? <https://github.com/TNT5562?tab=following>

What's the general process these days for doing a release and then finding that REFERENCE.MD is out of date?

the `release` rake task should warn you that it's out of date

now you could update it, push it to master, run the release task again. just don't tell anybody you did that

or create a new PR which updates the reference.md, add the skip-changelog label, run the release task