Puppet Community

and this is the first request for it I’ve heard :wink:

I can bring it up multiple times if that helps for your statistics :D

:wink: There’s some work being started now around the plan &amp; task workflows, I’ll feed the request along

if theres anything I should betatest <http://let.me|let.me> know

In general, I’ve love to have better tools for users to extend the console through tasks &amp; plans and keep the initial complexity of the console lower

we’re pretty close to having all the bits in place to allow user generated content that extends the console through tasks &amp; plans

:indeed: Next up is _Content and Tooling_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230606T140000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|112 hours>

OK, that’s a wrap for today - we’ll be back in a couple of weeks. Thanks for the suggestions!

:allthethings: _Content and Tooling_ is about to start up in 15 minutes

Hey everyone. The CAT team office hours start now until 4. Ping us any questions you have

what is .pmtignore? What does it relate to?

oh CAT modules don't have a .pmtignore anymore

so when you build a module with `puppet module build` or whatever it excludes files that are in .gitignore and in .pmtignore

.pmtignore is a way to filter files from official module releases but track them in git

now I've a few PE customers with &gt; 150 modules per environment and a good amount of the files is stuff that's useless on a puppetserver, for example .github

I think you don't use `puppet module build` anymore but pdk to build the official release? I don't know if pdk also supports the .pmtignore

i'll have a look to see if it supports pmtignore

<https://www.puppet.com/docs/puppet/7/modules_publishing.html#modules_publishing_prep-publishing-exclude-files>

pmtignore was around in some modules but should be gone now

excluding .github would save us a few thousand files and lower code-manager deployment times

related topic: I asked Ben for <http://forge.pupppet.com|forge.pupppet.com> adjustments /a puppet module spec. I would be nice if .pmtignore/.pdkignore uses an allowlist, not a denylist for files

i don't see any reason why we couldn't exclude .github. It doesn't add any value to customers. I'll raise this with the team :slightly_smiling_face:

there are probably a few other files, but I don't have a PE customer today and cannot check :disappointed:

feel free to ping me anytime with anything else you come up with/feel would be beneficial to exclude

I think this is finally ready to go.. just one last rebase and we will get it merged in before the end of this session :sunglasses:

nice 1, i've approved the ci, once green ill merge

I'm not sure how to fix those CI errors....

try running `bundle exec rubocop --auto-gen-config`, the limit that was set for `Metrics/BlockLength` was decreased in your PR which has caused rubocop to complain about previously OK blocks

I've tried to resolve that, hopefully that works

thanks for your massive efforts on this one!

a release will be cut shortly :slightly_smiling_face:

In theory this will help simplify lives ;)

nothing comes to mind Tim. Our release prep workflow generates a PR with a check list of things to check before you merge the PR, one of these is that the reviewer should check that the metadata version is correct

but nothing comes to mind for dependencies

<@U0332SZQLKZ> do you know if we have any dependency validation checks?

<https://github.com/ekohl/metadata_json_deps> that's what we use at Vox Pupuli. parses all local metadata.json files and prints you outdated dependencies

yeah we have a dependency validator that is meant to run as part of ci

<https://github.com/puppetlabs/cat-github-actions/blob/757c44b98c3aada0274b614daa5c3e032198eaae/.github/workflows/module_ci.yml#L72>

<@U3E3EMPUJ> wonder if this is something we can get added

also we should probably be using pdk there rather than bundle

Yep! This is something I will get ticketed up and get in as soon as we can :slightly_smiling_face:

<https://github.com/puppetlabs/dependency_checker>

and some customers like it if version constraints in metadata.json aren't violated

:indeed: Next up is _:teacher:Puppet Core Team_ in <https://www.timeanddate.com/worldclock/converter.html?iso=20230606T170000&amp;p1=202&amp;p2=179&amp;p3=919&amp;p4=307&amp;p5=3332&amp;p6=236&amp;p7=240|2 hours>

:kermit_typing: _:teacher:Puppet Core Team_ is about to start up in 15 minutes

Hi folks, sorry for the late start. Have a question about open source puppet, ask away!

I'll confess continued interest in:
<https://github.com/puppetlabs/facter/pull/2488>
<https://github.com/puppetlabs/facter/pull/2487>
<https://github.com/puppetlabs/facter/pull/2480>

About PR 2488, is `operational_state` Linux specific? Thinking about what it should be named if we wanted to show which interfaces were up/down on Windows or macOS?

It should be something Windows/MacOS report, but I don't actually have any of those to see how they state it.  It comes via RFC2863.

<@U1PC2RAH0> yep <https://tickets.puppetlabs.com/browse/PA-5549>

nice. can you roughly estimate when this is planned to be delivered? I had the first customer request today about

"we need to replace our debian 8 boxes"....

Here's a list of all additions and removals on our radar: <https://tickets.puppetlabs.com/issues/?jql=issuetype%20%3D%20%22New%20Feature%22%20and%20project%20in%20(PA%2CPC)%20AND%20labels%20in%20(os)%20and%20resolution%20is%20empty%20and%20%22Epic%20Link%22%20is%20empty%20ORDER%20BY%20Summary|https://tickets.puppetlabs.com/issues/?jql=issuetype%20%3D%20%22New%20Feature%22%20and%2[…]d%20%22Epic%20Link%22%20is%20empty%20ORDER%20BY%20Summary> I don't have an ETA for Debian 12 yet

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