Puppet Community

Hi,
I write a custom provider as SimpleProvider. What is the recommended way to execute a command and still be able to mock it for unit testing? I currently use Facter::Core::Execution but it feels wrong.

Also, how can I `confine` a SimpleProvider? I'm looking for the equivalent of `command:` and `confine:` of a low-level implementation.

I'm not sure about that. I'd probably look at what other resource-api based modules are doing

Unfortunately, I cannot find many implementations with SimpleProvider, and none of them seem to have any reference to a `confine`. For the execution, <https://github.com/voxpupuli/puppet-firewalld/blob/master/lib/puppet/provider/firewalld.rb#L46> suggests using Puppet::Provider::Command which I will try right now.

:meeting: Next up is _Content and Tooling_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230725T140000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|164 hours>

Ok folks that's a wrap, see you next time!

:businessparrot: _Content and Tooling_ is about to start up in 15 minutes

hey :wave:  our office hours start now. Send us any questions you have

i'm not sure if we own that. Let me see who does

are you not able to release as one of the code owners?

I have the permission but I dont know the workflow :)

i don't know the repo but it looks like you'll need to run the `auto_release` workflow which will create a PR for you which you can review and merge if you're happy with the changelog and versions etc. Then run the `publish_module` workflow to actually release the module on the forge

martin.ewings941 is on the rise! (Karma: 1)

Did not know that actually worked on this channel lol

are there really 940 martin.ewings’s before me?

See the `puppetlabs-influxdb` module at <https://forge.puppet.com/puppetlabs/influxdb?src=slack&amp;channel=office-hours>

:the_more_you_know: Next up is _:teacher: Bolt_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230725T220000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|7 hours>

that's it for the CAT team. See you next week :slightly_smiling_face:

Thanks, set the reminder :slightly_smiling_face:

good luck! I’m too tired to help you more today!

Thanks for everything, that’s helped with general understanding and research points

:fry_dancing: _:teacher: Bolt_ is about to start up in 15 minutes

I pinged internally to see if anyone recognizes it

what are you wanting to achieve with the `pwd` example?

That was just example, any command produce the same additional “errors” output

what user are you connecting as? If you ssh as that user, what happens?

Found the root cause couple of minutes ago:
<https://puppetcommunity.slack.com/archives/C7GP57T50/p1690382851363759?thread_ts=1690293878.042889&amp;cid=C7GP57T50>

If briefly, If I run this code from the _root_ user using `bolt apply` , it will fail:
```Puppet::Util::Execution.execute(cmd, :uid =&gt; uid, :gid =&gt; gid, :combine =&gt; combine,
            :custom_environment =&gt; { 'HOME' =&gt; home }, :failonfail =&gt; failonfail)```
That’s because `execute` is not changing the current working directory, which in this case is `/var/root`, (it <https://github.com/puppetlabs/puppet/blob/9614e6125cdaea692424e8962827fb882030d5cf/lib/puppet/util/execution.rb#L323|tries> to do `Dir.chdir('/var/root')`) which is private to the _root_ user. We don’t have that behaviour on `puppet apply`, because executing from the `/etc/puppetlabs/code`.

My fix is:
```Puppet::Util::Execution.execute(cmd, :uid =&gt; uid, :gid =&gt; gid, :combine =&gt; combine,
            :custom_environment =&gt; { 'HOME' =&gt; home }, :cwd =&gt; home, :failonfail =&gt; failonfail)```
```:cwd =&gt; home```

Not sure, but I thing there should be some guidelines or mechanisms to avoid this. Because it makes modules from `puppet apply` sometimes not compatible with `bolt apply`.

The Content and Tooling office hour has been adjusted. It will now alternate weekly between focusing on modules and on tooling, and between two different time zones for better coverage.

:meeting: Next up is _:teacher:Puppet Forge_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230727T180000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|43 hours>

:coffee: _:teacher:Puppet Forge_ is about to start up in 15 minutes

Hey! The forge validation API checks compatibility with Puppet 6 &amp; 7. I guess this will be updated to check for 7 &amp; 8 (is this on the roadmap)?

Related questions, are their plans to make legacy modules that had no update in years less visible in search results ? (I can't recall what I searched some times ago and the first result where not the most relevant).

we have quite a few plans around that, but they aren't concrete yet so I can't give you a roadmap

in general, we want to deprioritize, or maybe even remove content that is no longer useful

then we have several tools and algorithms for ranking quality

for example, my denmark project looks for project/repo smells that might indicate something like an abandoned project and can surface those