Puppet Community

<https://github.com/theforeman/puppet-foreman_proxy> grep for datacat in that repo

<https://github.com/theforeman/puppet-foreman_proxy/blob/5c9db9433d7215d3f1cce112b930062a854eb83b/manifests/feature.pp#L7-L10> &amp; <https://github.com/theforeman/puppet-foreman_proxy/blob/5c9db9433d7215d3f1cce112b930062a854eb83b/manifests/register.pp#L42-L50> are the most relevant bits

that is there to set the features property on <https://github.com/theforeman/puppet-foreman_proxy/blob/5c9db9433d7215d3f1cce112b930062a854eb83b/manifests/register.pp#L5-L13>

ah yes, I meant the Foreman project, not the Foreman module :)

you mean the one that has a foreman_puppet that does integration with Puppet, while puppet-foreman does setting up *with* puppet

and then puppetdb_foreman does the integration with puppetdb and should have been foreman_puppetdb?

yes, I'd love to rename puppetdb_foreman to foreman_puppetdb

check <https://github.com/voxpupuli/puppet-confluence/pull/211> for example, the CI doesn't pass and it needs to be fixed

and for logstash, check <https://github.com/voxpupuli/puppet-logstash/pull/408>

do we have a solution for templating `./examples/foo.pp` into the `README.md` ?

found yet another case of the readme being wrong

IMO: delete examples/ and every code snippet in readme.md, move it into the classes as @example puppet-strings block

so it gets automatically rendered into reference.md

I used to do that but I rather like using ./example/foo.pp for acceptance tests as that way the code fragment gets puppet-linted

I would like to use the same fragment in the readme and for the acceptance test

I thought about processing the readme to pull out the fragment but that doesn't work so well for linting

oh, well I was figuring I could give ewoud a $50 gift card :wink: