if you need to,

pdk bundle exec rake spec

can be helpful as well

if you need to,

pdk bundle exec rake spec

can be helpful as well

I'm not using PDK for anything real. When I tried using it, it changed the spec file which then make it a problem to contribute back to the original github repository.

I'd look at the docs for the module then

specifically for voxpupuli there's https://voxpupuli.org/docs/how_to_run_tests/

^ this if you use the vox pupuli tools (which I recommend)

prepending "pdk" to all of the "bundle" commands from voxpupuli docs is giving me some results. I see an awful lot of red, however. I'm farther along than ten minutes ago!

so, if you're not in a pdk converted module, pdk bundle may not do what you expect (but close enough)

Should I still use PDK for not-yet-converted modules then?

I'm of the opinion that if it works use it

I’m using PDK for all my modules and control repos (including bolt homelab repo).. it may need some workarounds but it works well for me

I'm trying to start contributing to voxpupuli. If I stick with PDK, will I be ok?

voxpupuli is not using PDK AFAIK

Grrrr....

they invented their own modulesync for the template management.. but better to ask on #C0W1Y5VL0

modulesync and the vox design predate pdk

Thanks, everyone. I finally managed to get some spec tests working -- if only "expect to compile" on a completely blank module! 😉

This message was deleted.

thanks for the correction

it all predates me 😄

....Annnnnd on a different topic: Am I correct in the generalized statement that this bit of containment effectively says, "Treat chrony::install resources as a bundle, chrony:config resources as a different bundle, chrony::service resources as a third bundle and then initialize the install ::resources first, the ::config resources second and the service resources ::third? I'm trying to wrap my head around containment.

....Annnnnd on a different topic: Am I correct in the generalized statement that this bit of containment effectively says, "Treat chrony::install resources as a bundle, chrony:config resources as a different bundle, chrony::service resources as a third bundle and then initialize the install ::resources first, the ::config resources second and the service resources ::third? I'm trying to wrap my head around containment.

it more says "include this class and the resources in this class are part of this class for dependency management"

if you

require => Class["chrony"]

it will also by relation include all `contain`’d other classes, this helps you say “do this thing once chrony is fully available

then it says do all things in

install

before

config

and should

config

change notiy all things in

service

(which would restart the service resource) and also ensures ordering is such that service is after config

however if install upgrades a rpm and the config doesnt change service wont restart (afaik)

however if install upgrades a rpm and the config doesnt change service wont restart (afaik)

This message was deleted.

check this readme.md: https://github.com/puppetlabs/puppetlabs_spec_helper