personally, I would only use eyaml if you can't run vault or some other key management... yes, otherwise I would point people at eyaml

yep. I prefer vault over eyaml

it's for a personal setup, I really just have 4 secrets now

vault feels like overkill

for that case, yea eyaml is probably a good choice

https://github.com/voxpupuli/puppet-grafana/pull/288 does that make sense? afisher?

Not sure. I've only ever confined a provider before, not the type itself.

hmm, maybe you're right

and this would normally be because the provider needs the gem in the agent ruby environment, and you'd like to install it in the same puppet run. I think here, it needs to be on the puppetserver environment only?

or the toml content should be generated in the provider?

I mean, a type can call the provider, right?

oh, it doesn't have a provider - it just generates a file resource with the right content

it's a common pattern, I wonder if that should be implemented more natively - like inheriting the file provider or something

I'm really confused by the whole PR that implemented this type. Was it even finished before being merged? The type exists, but then the configuration file is created in config.pp with an inline template...

hmm, good question

and I just wanted to do a quick release while going over some issues …

This message was deleted.

@natemccurdy can you take a look at https://github.com/voxpupuli/puppet-catalog-diff/pull/50? 🙂

can I get a review for https://github.com/voxpupuli/puppet-catalog-diff/pull/72/files :)

Hey I discussed with @Glenn Sarti about moving the puppetfile-resolver gem over to vox since he is no longer doing puppet work. While Vox does not use this gem currently it is a dependency for vscode plugin and bolt and maybe a few other community tools. I would like to propose we move this over to Vox while Glenn is reachable. Puppet will need to made aware of this @binford2k since it could impact future releases of bolt. What is the process of doing this and what work does Puppet need to do if any.

I would like to see Puppet investing money in maintaining tools 🙂

We maintain facterdb, rspec-puppet-facts, beaker, puppet-syntax, many puppet-lint plugins...

I'm not against having puppetfile-resolver within Vox. But I would love to see more investment from Puppet into the tools in general

This message was deleted.

This message was deleted.

This message was deleted.

ewoud, the use service_provider fact change in https://github.com/puppetlabs/puppetlabs-postgresql/pull/1303 seems to have broken tests for modules depending on puppet-postgresql :/

error during compilation: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, pick(): must receive at least one non empty value (file: /home/runner/work/puppet-foreman_proxy_content/puppet-foreman_proxy_content/spec/fixtures/modules/postgresql/manifests/params.pp, line: 85, column: 10) (file:

/home/runner/work/puppet-foreman_proxy_content/puppet-foreman_proxy_content/spec/fixtures/modules/foreman_proxy_content/manifests/pub_dir.pp, line: 15) on node fv-az135-302.uqcy5m2vj4pengxy1oencsd1xf.phxx.internal.cloudapp.net

(adding a custom fact in spec-helper now, but seems ugly?)