Allow resolution of trusted[certname] from factset

What's Changed

• Ruby updates by @dylanratcliffe in #332
• Allow resolution of trusted[certname] from factset rather than localhost by @chambersmp in #327

Full Changelog: v3.21.0...v3.22.0

Support ruby 3

What's Changed

• Fix typo by @DavidS in #313
• Fixed naming by @dylanratcliffe in #314
• Add onceover run spec --fail_fast option by @neomilium in #318
• Fix onceover with modern Ruby by @smortex in #326
• Onceover show Puppetfile - Add versionomy support for DSC module version format by @chambersmp in #328

New Contributors

• @DavidS made their first contribution in #313
• @chambersmp made their first contribution in #328

Full Changelog: v3.20.0...v3.21.0

Added support for external data

Onceover now supports facts that come from the trusted_external_data setting

Fixed Facter 4 factsets

Thanks to @genebean for this fix! Facter 4.0 changed how the puppet facts output looked, we can now handle this!

Revert manifest setting

Okay looking at these changes maybe this should have been a y release rather than a z... However I have limited time at the moment to fix so for now it's staying as it is. Changes are as follows:

• As per #292 the manifest option now defaults to nil as per the README
• Testing has now been migrated to GitHub actions
• Factset added: CentOS-8.3.2011-64
• Factset added: Debian-10.4-64
• Factset added: Debian-8.11-64
• Factset added: Debian-9.12-64
• Factset added: Ubuntu-20.04-64
• --trace option now properly propagates to r10k command execution for debugging

Rspec tags support

New Features

Rspec tags support

Tags created in the onceover config file are now propagated to rspec tags and the --tags option now affects both tags created in the onceover config file, but also any other rspec tags on any other tests that you might have put in your /spec folder.

Bugfixes

manifest option now works

The manifest option was previously not respected. WARNING: This could cause tests to break if you were previously relying on your site.pp not being read and parsed. If you are using site.pp to do classification based on facts or hostnames, and those facts or hostnames are included in your factsets, it will likely result in onceover testing two roles at a time instead of one and therefore breaking. I recommend that if you are affected by this you don't include whatever fact you use i.e. $facts['role'] in your factset. Onceover creates a variable for what it is testing called $onceover_class at global scope which might help if you were previously relying on a $role fact or similar. Alternately specifying a manifest directory that doesn't exist will also reset to the previous (technically incorrect) behaviour. This can be done permanently in the onceover.yaml file

Others

• #285
• #282

Fixed "erroor" typo

Whoops...

Added custom spec directories

As per #261 and #262 you can snow specify where to copy your spec files from before the tests run

Added Chocolatey facts 🍫

Thanks to @16c7x the default Windows factsets now contain enough chocolatey facts to run successfully if you're using the chocolatey module

Fixed tabular output

oncover show puppetfile now uses a different library for drawing tables which means that they aren't borked as per #273. Thanks to @smortex for this one! Also fixes #182