Puppet Community

but that needs an update: <https://github.com/voxpupuli/modulesync_config/blob/c0433f4d04fcb54355851c4424e8b441b2654e14/moduleroot/Dockerfile.erb#L11> is oudated

kind of weird we're using Ruby 2.7 but Puppet 6

bastelfreakas promised: <https://github.com/voxpupuli/modulesync_config/pull/816>

but of course CI is my personal nemesis...

it looks like the bundler cache might need to be flushed

can I have a review for <https://github.com/voxpupuli/puppet-varnish/pull/17> and <https://github.com/voxpupuli/puppet-varnish/pull/16> plz... both quite small

To prevent those sorts of README issues in the future, did we want a `rake` task to run `prettier` on the markdown files?

maybe voxpupuli-test is a good place for that

it would also be nice to require PRs to be appropriately labeled

I just started doing that at $day_job with a gha

```---
name: "Pull Request Labels"
"on":
  pull_request:
    types: ["opened", "labeled", "unlabeled", "synchronize"]
jobs:
  label:
    runs-on: "ubuntu-latest"
    steps:
      - uses: "mheap/github-action-required-labels@v3"
        with:
          mode: "exactly"
          count: 1
          labels: "enhancement, bug, skip-changelog"
          add_comment: true
          message: "This PR is being prevented from merging because of missing or incorrect labels."```

<@U11HA7VJ7> Was there any progress on 'trusted contributors' actually being able to merge code?  I think this was originally possible. re. <https://github.com/puppetlabs/puppetlabs-stdlib/pull/1301#pullrequestreview-1340295404>

I think someone wanted to check if trusted contributors could be added to the codeowners

I think it came up at a monthly meeting.  Maybe trusted contributors were going to be a separate group added to code owners??

yeah, ok, so I think we both remember it the same. :slightly_smiling_face:

I think, but I dont know for 100%, that you dsn only list grouos from the same org and trusted contributors are from a other org

Is <https://github.com/puppetlabs/puppet/commit/82cef2371352b648cc60aa7b7cedaa973c38ad35> going to be backported to Puppet 7?

Reading <https://groups.google.com/g/puppet-dev/c/hFIjgvOa5J0> I guess not.

So whilst we can make the option configurable in rspec-puppet it's not going to be especially useful at this time to try setting `include_legacy_facts` to anything other than what it defaults to based on puppet version??

Even with puppet 8 (main branch), I get
```Could not autoload puppet/type/service: Could not autoload puppet/provider/service/freebsd: Could not autoload puppet/provider/service/init: undefined method `downcase'```
if rspec-puppet-facts doesn't include legacy facts.

Does anyone know how to get a stacktrace when using rspec-puppet?