bundle exec rake spec

should work

I'm still getting the same "........................." output as the tests run.

or

bundle exec rspec spec/foo/bla_spec.rb

mhm I think the format is hardcoded to progress (which are those dots)

but there's a summary of all failures after the test is done

Is there a 'fail fast' option? I've tried --fail-fast but that's not an option.

I'm trying to submit a pull request to puppet-chrony but my tests are failing and it's taking 2 minutes to run the tests before the errors are displayed.

you can always abort it and then it will print all the failures that already happened

Thank you.

Here is my puppet-chrony pull request for a feature request (manage /etc/sysconfig/chronyd on RHEL family). I got all kinds of errors about "memoized helper". I tried to re-paramater-itize the spec file but there wasn't anything I could do to fix the rubocop warning. I was forced to put in the absolutepath to the /etc/sysconfig/chronyd file (part of the pull request). Can anyone recommend a change that will pass the rubocop checks AND eliminate the hard coding of the path I had to do in ./spec/classes/chrony_spec.rb?

Will there be a new release of stdlib anytime soon? Running into the

has_ip_address()/has_ip_network()

issue and would just like to use a released version vs git

Kind reminder for next week: Wednesday, October 22nd 2025: https://puppet.run Event in Hamburg, Germany. Talks will be done in English, unluckily no recording. You can use our Voucher Code “betadotsFREE” to get a ticket without costs. I am talking about different ways to test Puppet DSL code, Robert will talk about containers in Puppet development and Lennart will run a demo on automating icinga2. Besides this there will be presentations on Puppet Edge (a new feature in Puppet Core) , automating NIS2 compliance and managing systems in distributed infrastructure.

@Lukas Audzevicius hey, any chance you can merge https://github.com/puppetlabs/forge-ruby/pull/129 or point some people at it?

Hi folks, we've backported facter 4.15 to the public repo: https://github.com/puppetlabs/facter/pull/2795 It includes all changes from private facter except automation relating to puppetcore.

@josh maybe related: puppetserver-ca 2.7.1 was released to rubygems.org (https://rubygems.org/gems/puppetserver-ca/versions/2.7.1) on July 10th, but the repo was not updated since Feb 8th… 2024 (date of the release of version 2.7.0). I saw that unexpectedly working on the legacy Puppet ports on FreeBSD, not a big deal for me, just so that you are aware 😉.

Maybe from the private fork and it was forgotten to push the changes to the public repo?

Hi everyone ! Since doing the following :

if defined(Class['my_super_class']) {
     class { 'my_other_super_class': }
  }

Might result in an issue if the ordering in Puppet is not at our advantage, how would do the same thing ? I want to include a class, only if another class is already present.

Why?

That looks like an anti pattern

I have a main class that defines an application, and I want to make sure that if the node we apply on, has the log retrieval mechanism that we use, then we should add the small snippet of configuration for this application logs to be retrieved.

It might be an anti-pattern, but I don't really see a way to do that properly

The resource that adds the small snippet should fail with an informative error (and no change) if the overall mechanism is not present.

But I don't want the small snippet to be required for the application.. It's like that

[my_application_class]              [my_global_logs_conf_class]
   if my_global_logs_conf_class
     [my_small_logs_class]

But

my_application_class

should not fail because the

my_global_logs_conf_class

is not declared.. Maybe on this node we don't want to have the log mechanism that we have on other nodes

is this an application config settings ng? make a template.

vscode extension says that it uses puppet-lint and yet the editor is unhappy with idents and latest puppet-lint is fine. Some setting is missing?

Different linter versions?

It seems extension bundles it. I don't see a way to tell it to use a new one

Hello, everyone. What is a recommended approach to cleaning up puppet code? I have tried puppet-lint with

--only-checks ghostbuster_classes,ghostbuster_files,ghostbuster_templates

, but, for some reason, not getting any results. I’m sure i have some unused templates, manifests, etc… My google search is not pointing to any else useful. Any suggestions? Thank you!

VoxBox is probably your best bet long term https://github.com/voxpupuli/container-voxbox. But I and many others are still using the latest public release of the PDK.

pdk validate

will run the linters, and adding

-a

will do autocorrect

Also the community Slack is more active and a better place to get feedback these days https://voxpupuli.org/connect/