Puppet Community

Seems to throw error while trying to connect to the forge

looking at the logs, it more looks like some jenkins plugin fubar

and as I described, the jenkins plugins are still fubar - I documented that in the commit

(that's a recurring trend, also with real deployments :()

ideally we'd adopt <https://github.com/jenkinsci/plugin-installation-manager-tool>

I would love to see us adopt casc centrally on puppet-jenkins too (maybe not _required_ but a really clean config as code design to let puppet mostly manage jenkins via the api / xml files would be amazing

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

<ttps://plugins.jenkins.io/configuration-as-code/>

<https://plugins.jenkins.io/configuration-as-code/> even

That's what my company is doing.  Puppet is used to start a jenkins docker container, and manage some secrets etc.  But most of the configuration is done with casc as part of the docker image we build.

we actually built a profile that does casc in it

<https://docs.google.com/document/d/1rD1-HC36qNZL5FXEeSE1rtTjMHM45O6ylk3xwBmZDFg/edit> vox pupuli office hours is live!

afisher: I guess you're right, looks like it just uses diff &amp; the viewer. <https://dev.to/camptocamp-ops/automated-puppet-impact-analysis-1c1>

bastelfreak: <https://github.com/puppetlabs/content-and-tooling-team/discussions/76#discussioncomment-2723940>

Could someone review <https://github.com/voxpupuli/puppet-augeasproviders_grub/pull/69> ?  The modulesync PR still needs some work so I've done the regrettable thing of generating a manual CHANGELOG update.

I was concerned that #57 might cause breakage for someone

but I don't have strong feelings about it

It is a bug fix... but it could suddenly start changing someone boot config

:facepalm: That module doesn't have the release action in it either

Should <https://github.com/voxpupuli/puppet-augeasproviders_grub/pull/66> be rescued or is it better to start over?

I suggest running rubocop safe autofix and then generate a rubocop todo file for the remaining offenses. that's relatively easy. but afterwards the rspec 2 stuff needsto be ported to rspec3 I suppose

also you can propose another PR just with the release action and maybe Gemfile/Rakefile and we should be able to kick of a release

rspec completely blows up for me locally
```  Could not autoload puppet/type/kernel_parameter: Could not autoload puppet/provider/kernel_parameter/grub2: Missing augeasproviders_core module dependency```

check <https://github.com/voxpupuli/puppet-augeasproviders_apache/pull/11|https://github.com/voxpupuli/puppet-augeasproviders_apache/pull/11>

I started fixing some of the issues there and most of it applies to all the augeas modules

please check the github action and gemfile in the apache augeas pr. I hacked it to install auges libs/rubygems

I've gotten rubocop errors fixed for ./lib and created a TODO for ./spec.

When I change the mocking framework to mocha something odd is happening

```  1) Puppet::Type::Kernel_parameter::ProviderGrub2 finds grub2-mkconfig
     Failure/Error: allow(Puppet::Util::Storage).to receive(:store)
     
     NoMethodError:
       undefined method `allow' for #&lt;RSpec::ExampleGroups::PuppetTypeKernelParameterProviderGrub2:0x0000000002ed7e28&gt;
       Did you mean?  all
                      all_of
     # ./spec/fixtures/modules/augeasproviders_core/spec/lib/augeas_spec.rb:18:in `block (2 levels) in &lt;top (required)&gt;'```

not sure why it is descending into spec/fixtures/modules

--exclude-pattern doesn't seem to stop it either... wtf

the whole testing for those modules is a bit special and Inam far away from being an auges or types or rspec expert :(

I converted one file by hand from mocha -&gt; rspec-mocks and that seems to work

I found this set of cops but they didn't work for me: <https://github.com/andyw8/mocha_to_rspec>

I did it by hand... I am really bad at repetitive tasks... <https://github.com/voxpupuli/puppet-augeasproviders_grub/pull/66/commits/101b21850ab20ed9adfd5b9ba37a414e0f31c116>

any idea why the build of ruby-augeas is failing?  I'm guessing it needs augeas headers

this is pretty cool, <https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/>