14 is missing but 15 is already there?

yep

interesting

perhaps 14 is not LTS and 15 is?

ah this puppetdb module is really.. special

yes it is

https://github.com/theforeman/puppet-puppet/pull/882 I added some examples for puppetdb integration

can I get a review for https://github.com/voxpupuli/puppet-r10k/pull/609

seems odd that only one params treated differently

and https://github.com/voxpupuli/puppet-r10k/pull/610

I will move all others to init.pp as well

curios, is ignore spec something that is enabled in PE?

but that's one I also had to change

it's enabled in PE 2019.something and newer

https://www.puppet.com/blog/code-manager there

This message was deleted.

when the puppetfile entry for the module won't change PE thinks everything is fine

that's why I didn't enable incremental deploys in puppet/r10k by default

See the

puppet-r10k

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

I was wondering why my envs have missing modules...

This message was deleted.

I think it's a bad pattern that non-urgent bugs need to be submitted via a support ticket. those are private. When I identify a bug I want to check if others already found it. I cannot do that via the support portal. Only through jira. Also I want to fix bugs and provide a patch, but the puppet_enterprise module & related modules are hidden...

and when I raise an ENTERPRISE ticket in jira they are usually ignore or forked internally and only the fork gets updates

and I won't stop complaining until I get a sufficient answer why this workflow exists or until the workflow changes :D

https://github.com/voxpupuli/puppet-r10k/pull/612 now that's ready

https://github.com/voxpupuli/puppet-r10k/blob/master/templates/r10k.yaml.erb mhm really the worst way to construct yaml

that is begging to be replaced with a to_yaml()

like... https://github.com/voxpupuli/puppet-r10k/pull/613 ? :)

(still needs to be tested)

ha! looking good