Puppet Community

without a .sync.yml the `ruby-augeas` gem will get lost when modulesync is run. I would suggest adding a `.sync.yml` as the first commit on the branch. Then running modulesync and then committing the results of just `bundle exec rake rubocop:auto_correct` as that will make it much easier to ignore the noise during code review.

The `rubocop` error is actually the least of my worries at the moment. The bigger issue is trying to get the spec tests to run locally without needing to skip two  of them. Once that can be done, then the rest is just churn.

<@U11L48K6J> see <https://github.com/voxpupuli/puppet-augeasproviders_grub/blob/master/.sync.yml>

which will probably fix other errors as well

I'll give it a go and see what happens for sure :thumbsup:

<@U11L48K6J> On a completely different topic, is a simp/mate release coming soon?

See the `simp-mate` module at <https://forge.puppet.com/simp/mate?src=slack&amp;channel=voxpupuli>

Hey, that goes in <#C11LCKKQ9|forge-modules> :trollface:

Ummmm..... maybe? We're wrapping up SIMP 6.6.0 so some things got shifted a bit. I can check on the status though.

Naively, it looked me as if it was ready to go.

Woot! <https://forge.puppet.com/modules/simp/mate> One less fork in my Puppetfile...

If you uncomment the `skip`s and run `bundle exec rake spec` you'll see the fireworks.

<https://github.com/voxpupuli/puppet-augeasproviders_core/blob/master/spec/lib/augeas_spec.rb>

I ran `msync` it said there was nothing to do

it created an modulesync branch... hold on

I pointed it at your branch. <https://github.com/voxpupuli/puppet-augeasproviders_ssh/pull/74/commits/9136057843ddfeff81d9452a60464ab9154d5b1b>

Yeah, I don't see anything that would make a difference

It seems to be in the migration from whatever mocking language was used previously to the one that Vox uses

I can't, off hand, remember which is which

sorry, a ceph cluster decided it was lonely and I need to deal with it

<@U1QVBAUS2> Figured out the issue. Had to get the library load order juuuuust right

:thinking_face: I think this might actually break IRL since the override has to be loaded after the `sshkeys` module and they're loaded alphabetically. But there aren't any acceptance tests so :party_poop:

Oh, well, there are but it doesn't test that :shrug:

well, a new release isn't going to be any more or less broken than the current forge release...

<@U1PC2RAH0> I will look at the issue I just raised myself.. it's mostly I was shutting tabs and needed to record it.

<https://github.com/voxpupuli/puppet-vault_lookup/issues/56>

anyone knows what's up with the thias-libvirt module?

See the `thias-libvirt` module at <https://forge.puppet.com/thias/libvirt?src=slack&amp;channel=voxpupuli>

<https://github.com/thias/puppet-libvirt/issues/74> mentions transfering ownership to voxpupuli, but that didn't seem to have happened

meanwhile, there's a pile of pending PRs and the module doesn't work in debian stable

<https://github.com/thias/puppet-libvirt/network> is a complete mess

the answer is example42 chose <https://forge.puppet.com/modules/cirrax/libvirt> instead and i should use that too

anarcat: I've a profile that installs libirtd + starts the service