Seems both options are bad

either discard or combine

I wonder if some other method can be used instead

Welp, I'm going to have to get back to documenting the k8s module at a later point, need to get some food in me and then get my badge for ESA

@genebean Ananace (on IRC) is the Matrix wiz who offered to help us research and set up a bridge. We should set up some time for us all to chat about possibilities.

Sounds great to me!

I'll be a bit busy with this charity event until the 26th, but I'd love to chat with you guys when possible.

Ananace: sounds awesome. Not a huge hurry on it, so next month is totally fine

Ananace: besides, I'd rather see your k8s module make it past the gate first!

Well, it's now officially living at https://github.com/voxpupuli/puppet-k8s - so it's taken the first steps

(Needs to have its title changed though, forgot to do that before migrating it over)

and the description in about :)

hi all i just tried to do a release of the dnsquery module but i think there are some forge permissions that still need sorting out, or im missing something. can some one take a look and point out where im going wrong. cheers

can I get a review for https://github.com/voxpupuli/json-schema/pull/490

and https://github.com/voxpupuli/beaker/pull/1759 please :)

beaker one looks good to me, less familure with the json-schema repo though

jbond: https://github.com/voxpupuli/puppet-dnsquery/blob/master/metadata.json#L2 needs to be puppet-dnsquery, because

pupet

is our forge account

*puppet

Best practical joke ever

thank bastelfreak v4.0.0 puppet-dnsquery relesased https://forge.puppet.com/modules/puppet/dnsquery

See the

puppet-dnsquery

module at https://forge.puppet.com/puppet/dnsquery?src=slack&channel=voxpupuli

morning

ewoud: can you take a look again at https://github.com/voxpupuli/beaker/pull/1767 when you've some time?

Hello, we are discussing some issues with a customer around PDK, they are having issues with the top_scope_facts check from https://github.com/mmckinst/puppet-lint-top_scope_facts-check which is included with https://github.com/voxpupuli/voxpupuli-puppet-lint-plugins It had been suggested to me this particular check is not being maintained but I wanted to check what was known and to raise an issue with it https://github.com/mmckinst/puppet-lint-top_scope_facts-check/issues/13 We are being pushed for this to be resolved by the next release of PDK (weeks) and were wanting to find out best options / approach.

is that error really coming from the top_scope_facts plugin and not https://github.com/mmckinst/puppet-lint-legacy_facts-check ?

is that error really coming from the top_scope_facts plugin and not https://github.com/mmckinst/puppet-lint-legacy_facts-check ?