bastelfreak: for "control repo testing" I use https://github.com/theforeman/foreman-infra/blob/master/puppet/Rakefile & https://github.com/theforeman/foreman-infra/tree/master/puppet/spec/fixtures

thanks, will have a look

no fixture setup at all, just symlinks and regular module installation using g10k

our test modules are git submodules so that's all outside of fixtures

bastelfreak: oh, I should have also linked https://github.com/theforeman/foreman-infra/blob/master/puppet/spec/spec_helper.rb since there I just set the correct module_path

ah you don't use puppetlabs_spec_helper

that also sets module_path and it felt like I couldn't overwrite it. but maybe something else was wrong as well

yes, it might be good to write an equivalent of https://github.com/puppetlabs/puppetlabs_spec_helper/blob/main/lib/puppetlabs_spec_helper/module_spec_helper.rb that's control_repo_spec_helper.rb

yeah

testing control repos is always interesting

in an ideal world, you would get all available roles + their factsets from puppetdb, run acceptancetests for changes and catalogdiff

there is let(:node) in rspec-puppet, I wonder if you could work that up further

I’ve just pushed this https://github.com/puppetlabs/puppet-strings/pull/333

#333 (GH-332) Ensure PuppetStrings is loaded for tasks Pull request opened by chelnak Prior to this PR users would receive an Undefined Constant error when attempting to generate a reference file via the provided Rake tasks. This was caused by the compact testing style for modules added in v3.0. In this case the parent, PuppetStrings is not properly loaded before Tasks. As a result the error above is caused. This PR adds a new module declaration to tasks.rb that will ensure that the PuppetStrings is properly loaded. puppetlabs/puppet-strings ✅ All checks have passed 3/3 successful checks

I think I finally figured out how to properly implement idempotent apply with proper debugging in acceptance tests

it always bothered me that you only saw the last few lines, which made debugging hard

ah awesome

and sometimes you want additional context, like run cat /var/log/something

let's see if I can submit a PR

so https://gist.github.com/ekohl/3763bd669bbbce2502648709ec5160f1 is a matcher that allows you to write it { expect('include motd').to apply.idempotently }

neat

question is: where should it live? beaker-rspec, beaker-puppet or voxpupuli-acceptance?

I'm leaning to beaker-rspec

I would say that beaker-puppet makes slightly more sense then beaker-rspec, only because someone not using puppet might be using beaker-rspec? (maybe. very maybe)

I think beaker-rspec makes the most sense

https://github.com/voxpupuli/beaker-rspec/pull/115 - I started this because I was missing feedback in Litmus but couldn't test it so I wrote it for Beaker

This message was deleted.

Hi all Is it possible get new release of https://github.com/voxpupuli/puppet-confluence and https://github.com/voxpupuli/puppet-logstash to the forge? The current 4.0.0 version of puppet-confluence has a dependency to puppet/mysql_java_connector < 4.0.0 which locks puppetlabs/stdlib to 5.2.0 ... The current The main branch seems to cover my needs.

Hi all Is it possible get new release of https://github.com/voxpupuli/puppet-confluence and https://github.com/voxpupuli/puppet-logstash to the forge? puppet-confluence 4.0.0 has a dependency to puppet/mysql_java_connector < 4.0.0 which locks puppetlabs/stdlib to 5.2.0 ... elastic-logstash 6.1.5 depend on puppetlabs/stdlib < 6.0.0 as well. The modules main branches seems to cover my needs right now.