Puppet Community

are there plans to bump the rubocop version? It's currently pinned at 1.48: <https://github.com/puppetlabs/pdk-templates/blob/main/config_defaults.yml#L533-L534> . At Vox Pupuli we bumped to `~&gt; 1.50.0`. That's the latest version supporting Ruby 2.6

As far as I'm aware there are no plans to move the rubocop pin in the immediate future but it is something that will be looked at regularly.

It was the newest released version at the time we planned out the update.

In this previous talk, we agreeded in a roadmap:
1. Implement stream management in Forge's yum module
2. Implement multi-profile management in core `package` resource `dnfmodule` provider
3. Deprecate stream management in `dnfmodule` provider

Also, a good revamp of the docs is in order

I think we can merge the PR when you added some docs/explanations to the README.md

it was open long enough and nobody complained

<@U1PC2RAH0> There is one complaint from <@U1QVBAUS2> about overlapping step 1 with current `dnfmodule` provider. I invited him to the Slack talk, so he could see the full reasoning.

I just don't know how to move forward on the talks in the PR itself. Could someone help there?

I mean, besides restating the current issues with `dnfmodule` and our roadmap

<@U1PC2RAH0> Oops, you already commented that in the PR, but I overlooked. Will do that right now.

Just to be sure: you mean the root README from yum module project, correct?

we need to ensure that others can easily understand why this code exists

otherwise in a year someone will purge it and say 'hey core package type already can do this'

Should this reasoning go into a README subsection inside "Usage"?

<@U1PC2RAH0> <https://github.com/EmersonPrado/puppet-yum/tree/issue_310#dnf_module_stream-resource-versus-dnfmodule-provider|Done>

I reviewed <https://github.com/puppetlabs/puppet-lint/pull/142> yesterday and like the idea, but I was thinking about the best place to document (new) linter options/plugins

thanks for reviewing! Still tidying it up atm but it should be ready soon.

We have a puppet-owned version of that docs site and plan to add documentation for this plugin there. I'll grab the link

<https://puppetlabs.github.io/puppet-lint/plugins/>

mhm I should probably update <https://voxpupuli.org/plugins/#puppet-lint>

yes. Once it's all merged and ready to go, i'll document our <http://puppet-lint.com|puppet-lint.com> and let you know :slightly_smiling_face:

<@U1PC2RAH0> we have plans to move these things into more official documentation in the future too

:waiting: Next up is _:teacher: Bolt_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230822T220000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|7 hours>

:allthethings: _:teacher: Bolt_ is about to start up in 15 minutes

:goodnews: Next up is _:teacher:Puppet Forge_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230824T180000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|43 hours>

if your code is under any version control it’s safe because PDK will just drop some files into your module directory.. biggest issue from my experience was spec_helper.rb overwritten :slightly_smiling_face:

but anyway, it’ll write the changes expected to a file first (convert_&lt;something&gt;.txt or so)

you can cancel the conversion then and read that file carefully

then you can tune the default template via .sync.yml or maybe you can decide to create your custom template

anyway.. it’ll not touch your code.. at least I don’t remember any issues wrt that.. it’ll just drop some tool configs around

then instead of `bundle exec ...` you can use either some pdk commands (`pdk validate`, `pdk test unit`) or `pdk bundle exec ...`

check the default template for details of what is going to be changed in your module dir: <https://github.com/puppetlabs/pdk-templates/tree/main>

Ok, thanks... We hardly make any use of the gem file actually. So this operation just generates some separate files for the validation to use?

if there are no unit tests, no CI/CD configs, no Gemfiles - you wont notice any changes I believe (except more strange files appeared)

just copy your module somewhere and do the `pdk convert`, you’ll see

Ok, well. We have not used many of the more advanced devops features, actually. And this is the first time we are trying to do a in-place upgrade. So we want to be sure we don't mess up. :slightly_smiling_face: We have previously set up a new server and migrated the nodes one by one... A tedious exercise to say the least.

maybe check <#C1TTFG16G|> or <#C19V5U41Z|> channels also

Yes, we'll have a vmware snapshot, a normal backup, and the git-repo also. Better safe than sorry... Thanks for your input! :slightly_smiling_face:

good luck with the upgrade! I’m not experienced with PE so cannot say much about.. but PDK is nice :slightly_smiling_face:

Ah, one more question... :-) Can we still use "pdk validate" to check if our code syntax is compliant with new version even if we havent written any unit tests?

Yes, validation and unit tests are different things

Validators are for syntax and code style. Unit tests are for testing the logic (that your code does exactly what you expected)

Thank you! Even though I have worked with Puppet for 5 years now, I still feel like a...muppet. :slightly_smiling_face: Have a nice day!

Yury as always is spot on :slightly_smiling_face: Just to note as well Goran you can add the basic default unit tests with PDK running `pdk new test &lt;class name&gt;`This will add an rspec test to check the code will compile with default facts / variables

I recommend reviewing the list of files it will create, if you're not using various CI utilities, you may want to add them as disabled in .sync.yml

:waiting: _:teacher:Puppet Forge_ is about to start up in 15 minutes

(context; that's my internal profile photo for zoom and everything)

sure, let's pop that over to <#C0W1Y5VL0|> and get some eyeballs on it

:businessparrot: Next up is _:teacher:PE Console_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230824T210000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|2 hours>

:fry_dancing: _:teacher:PE Console_ is about to start up in 15 minutes

\o Good day y’all - console office hour has begun!

sorry I’m a bit late, release day and all!

If you have any questions/suggestions for anything related to the console, any of the console services (RBAC, Classifier, Activity Service) or the Orchestrator, ask away.

Everyone enjoying the new platforms (Ubuntu 22.04 and EL-9)?

so controversial question about the console