Puppet Community

it seems to be closer to 1s where I've tested. That seems like alot

```Offenses:

spec/unit/facter/udev_spec.rb:84:27: C: [Correctable] Layout/SpaceAroundOperators: Operator =&gt; should be surrounded by a single space. (<https://rubystyle.guide#spaces-operators>)
              'property'  =&gt; include(
                          ^^```

```Offenses:

spec/unit/facter/udev_spec.rb:84:15: C: Layout/HashAlignment: Align the keys and values of a hash literal if they span more than one line.
              'property' =&gt; include( ...
              ^^^^^^^^^^^^^^^^^^^^^^

40 files inspected, 1 offense detected```

sorry, that output was without autofix... but that is what it is doing

no idea why it is upset about this one hash one the dozens of others in the same file don't do this

I've tried to organizing the keys several ways

looks like a parser bug as the hash it is upset about now only started after I added a hash above it

gezbuz, finally find a hash key order to makes it happy

<@U1PC2RAH0> do you want to take another look at <https://github.com/voxpupuli/puppet-systemd/pull/292> ? Most of the changes I've made are to the unit tests.

oh, need to remove a the caveat on the fact... that's no longer true

<@U1PC2RAH0> Do you mean confining on the existence of the file `/usr/bin/udevadm` ? I thought there was no guarantee that would be the path.

I've been bitten by debian having separate /bin /usr/bin in the past

huh. First time I've seen this happen:
```-- Add support for strict mode for DNS over TLS [\#200](<https://github.com/voxpupuli/puppet-systemd/pull/200>) ([wobblesprout](<https://github.com/wobblesprout))>
+- Add support for strict mode for DNS over TLS [\#200](<https://github.com/voxpupuli/puppet-systemd/pull/200>) ([ghost](<https://github.com/ghost))>```

<@U04LKDWA46S> FYI - <https://github.com/voxpupuli/puppet-systemd/pull/312>

no but yes. We're actually going to be working on that over the next month.

what I can say now is that there are approximately 5k infrastructures/sites globally who are
1. running super new open source puppetserver (within ~8 months or so)
2. using the packages that we built and shipped
3. who haven't turned off content telemetry
4. and have a network that allows outbound https connections

each of those has an unknown multiplier, so the true number is likely much higher and we don't have a good way yet of extrapolating that

and each of those will have agents. We have the data, but I haven't done the query to sum them up yet.

(all this is/will be in the public dataset fwiw. It's all anonymized and aggregated so we can share it publicly and you can run your own stats)

Interesting. I didn't think there would be a complete data set.  What I was trying to do was get an idea of how many hosts might be touched by a change to a mod.

I mean, it won't ever be "complete" but answering questions like :point_up: is exactly what it's for

```SELECT slug, version, SUM(count) AS count
FROM `dataops-puppet-public-data.aggregated.module_usage_count`
WHERE slug = 'puppet-systemd'
GROUP BY slug, version
ORDER BY count DESC
LIMIT 1000```
<https://docs.google.com/spreadsheets/d/1kYbXs9ULqugwDioykL2Zj7MMxDcsamwBBYZNK3scOD8/edit#gid=930178631>

oh, indeed, that is exactly what I was wondering

more interesting question: how many people still use camptocamp/systemd

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

the _kind_ of info we can get like this is pretty limited, tbh. We can find volume of usage, but can't track back to who or do update notifications, or anything like that.

puppet-systemd -&gt; 426k
camptocamp-systemd -&gt; 543k

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

This is where I was going with that: <https://docs.google.com/spreadsheets/d/1GUHXhjKaM13PjHoppsTOAJXp22hT6tjmpqEakReKWzo/edit?usp=sharing>

I've been thinking that I'd actually like to set a schedule for the agent run interval.  I probably don't need 30mins in the middle of the night. In fact, I probably would be better off without the agent running at all in the middle of the night for most hosts.

many customers I maintain switch to noop during the night

anyways... my guess is that if/when r10k gets constraint solving support that all of a sudden people will update their Puppetfiles to switch away from camptocamp

<@U1QVBAUS2> <https://hachyderm.io/@binford2k/109753179773569551>

I know you've been working on it :wink: Excited for the day it arrives

you can use the standalone tool today -- I have a PR to add it to core r10k, but there's disagreement on the UX &amp; workflow and nobody is currently prioritized to focus on it.

I've got gha running both r10k and puppet-lint for my main control repo now as a way to prevent problems from creeping into my Puppetfile

but, rather obviously, most people aren't doing this

<https://github.com/voxpupuli/ra10ke|https://github.com/voxpupuli/ra10ke>

yes I know about them... no I don't use them purely because I put something in the control repos Rakefile before it existed

but then I do things like spend 3 hours trying to bump module versions

na dont say that. Quality over quantity. Also every contribution counts

so looking forward to having version ranges in my Puppetfile...

especially symbolic ones liks &gt;=ancient &lt;= crusty. That's my company's sweet spot

hey <@U1PC2RAH0>,I don't install modules from github via release packages, but can't help but notice that 8 months ago 2.0.0 was released, but 0.6.0 is the latest github release.

<@U2HGUG2CD> for which module? we usually dont create github releases. just tags. when tags exist then because the previous owner did it

oh, sorry, the one you were previously speaking on: ra10ke

:facepalm: wow, I said module adding even more confusion. Sorry.

I don't think that is the changelog generators fault... the github account was deleted?

bleh, with puppet-systemd 4 we broke some modules :(

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