Puppet Community

and there are no `debug` logs _anywhere_ in the code so <@U11LEJ0TC> has gotten me twice :slightly_smiling_face:

Created a PR to fix this one: <https://github.com/voxpupuli/puppet-rsyslog/pull/209>

afisher: modulesync now has `msync exec` as a command - abuse that? ;)

<https://github.com/puppetlabs/puppetlabs-vcsrepo/pull/586> anyone happens to have access to that repo and can approve CI?

I still think <https://rspec-puppet.com/documentation/> has always been a good place to start

for example, I just happened to look over the docs for classes and noticed node_params, to simulate an ENC which I'm pretty sure I haven't used before but should in some places

<@U1PC2RAH0> not sure what’s worse, all this new code, or including the gpg key in the module :grimacing: <https://github.com/puppetlabs/puppetlabs-docker/pull/885/files>
seems like there should be a better way

I was going to… "borrow" some code from facter, and found out that it doesn't consistently work.

on FreeBSD, which no one but me and smortex care about, but still

I care about FreeBSD, but not about Puppet &gt;.&lt;

_sees some venn diagrams of what Zhenech cares about_

well, we know at least that Puppet and FreeBSD are there, but do not overlap

Zhenech: how do you manage your FreeBSD machines?

Zhenech: unfortunately, I'm allergic to YAML. similar to: <https://github.com/ziglang/zig/pull/14265>

very related: <https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell>

(most should be known, but it's a nice summary)

Zhenech: just looking at this, i can already guess how horrific this is going to be

the mistake they made was "let's make things easier for humans to input" and actually made a lot of things ambiguous

the sexagesimal (base 60) numbers can also be hit when using MAC addresses for example

I typically just quote things just to be safe and avoid having to think