I do: https://github.com/voxpupuli/modulesync_config

or at least your own

.sync.yml

but then you open a third party module …

things like this trigger me: https://github.com/voxpupuli/pdk-templates/blob/bb554cbb831d8c651cd54056ac09950228603e5e/moduleroot/spec/spec_helper.rb.erb#L57-L59

there's already https://github.com/puppetlabs/puppetlabs_spec_helper/blob/6d49745eb3b5e4bcceaf91f166ec27a543fd5f91/lib/puppetlabs_spec_helper/module_spec_helper.rb#L80

but that's even weird because rspec-puppet has a proper option for that: https://github.com/puppetlabs/rspec-puppet#strict_variables

Raise a PR into templates repo to use RSpec option instead

yes, but that's how I always get distracted

somehow I was sure RSpec config option was used 🤔

I just want to use restic, not fix infrastructure :(

and now I woner why there's no option for strict in rspec-puppet

at least I've opened https://github.com/puppetlabs/rspec-puppet/issues/47

and https://github.com/puppetlabs/puppetlabs_spec_helper/pull/389 should fix another part

https://github.com/puppetlabs/puppetlabs_spec_helper/commit/6dd1f530a97c3005be1a480472bdb1ef1ba7fd0e is also an interesting one: I wonder if that should have also been done in rspec-puppet

TY for that! 🙇🏻

I'm trying to integrate voxpupuli testing in my new Puppet module and am having a problem with the Github action. The puppet-lint scanning job is failing because it can't resolve a dependency on rubocop-spec. This is new territory for me and I'm unsure how to go about resolving the problem. I created my module with 'pdk new module' (or something like that) so I'm sure I've got a lot of cruft that doesn't need to be there. I've checked out puppet-chrony for clues on how to get my Github action working but so far I'm at a loss. My best guess is a hardcoded version of rubocop and related gem files but there are several hard-coded gems in there and I'm afraid to start poking around. Any suggestion or pull request is much appreciated to get me over this hump.

where is the code it ran on?

is that https://github.com/bschonec/puppet-ivanti/tree/8-implement-voxpupuli-ci-cd-tests ?

yes

I copied puppet-chrony Gemfile verbatim to my Gemfile and the puppet-lint scanning action succeeded.

See the

puppet-chrony

module at https://forge.puppet.com/puppet/chrony?src=slack&channel=voxpupuli

Well, succeeded in ruby related stuff. The puppet-lint failed due to some syntax issues in my manifest.

what I'd start with is cloning https://github.com/voxpupuli/modulesync_config, run bundle install, change managed_modules to bschonec/puppet-ivanti and run bundle exec msync update --noop -b 8-implement-voxpupuli-ci-cd-tests

right now I'm trying that out, but running into https://github.com/voxpupuli/modulesync/pull/260 myself, so one moment

Yikes! That sounds daunting for a noob like me. Thank you. I'll try your suggestion and report back.

I've often wondered about structuring our repo so you could use PDK, but I never bothered myself since I refuse to use PDK since sends analytics by default

but after you do that, you should be able to see a git checkout in modules/bschonec/puppet-ivanti with all the files templated according to Vox Pupuli's CI setup

I didn't check the details, but https://github.com/bschonec/puppet-ivanti/pull/3 is what I'd start with

Thank you. I think this will really help me to start moving forward with Voxpupuli.

oh, and I think .devcontainer should also be dropped