or I suppose you could have a set of rules for constructing "sub envs" per host that dynamically update when an agent phones home with its set of facts

with a custom report processor you can get notifications about new reports and new systems

whats the purpose of the sub envs you have in mind?

I want less envs, not more (mostly because of memory footprint)

I am partially fixing the huge environment thing by creating a set of basemodulepath deployments for modules I know will be shared across my org

so all of the basic infrastructure modules and profiles live there (all the way up to puppet/nginx and puppetlabs/postgresql etc) so that the environments really only have to implement hiera and their application modules

See the

puppet-nginx

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

I've got a module called, "brian" with ../data/common.yaml with the value brian:my value "Hello, world." When I

notify {"hello, ${my_value}, ${brian::my_value}.":}

inside the init.pp, I get an empty string. Is it required that I declare the brian::my_value in the class module as "String $my_value"

yes, or use a hiera lookup() of brian::my_value

Thanks!

@Brian Schonecker +1 for adding a parameter if it's intended to be adjusted by the user. Otherwise no need to put it in hiera: just hardcode it. There are very few legit usages of

lookup()

IMHO

What I'm trying to do is modify the puppet-module-pam module so that it will accept an array of "modules to run" so that I can limit how many changes the module makes. I want to use the limits.d functionality of the pam module but I don't yet want to make any changes to /etc/pam.d files. My thinking is that if I have an array of "submodules" that I want the PAM module to run, I can ease into managing PAM entirely. https://github.com/bschonec/puppet-module-pam/pull/1

What I'm trying to do is modify the puppet-module-pam module so that it will accept an array of "modules to run" so that I can limit how many changes the module makes. I want to use the limits.d functionality of the pam module but I don't yet want to make any changes to /etc/pam.d files. My thinking is that if I have an array of "submodules" that I want the PAM module to run, I can ease into managing PAM entirely. https://github.com/bschonec/puppet-module-pam/pull/1

Heck, sorry. I didn't realize until now that I posted this in voxpupuli.

Hello, would anyone have time to review this PR? I think that would be a good addition for that module and any that use it as a dependency https://github.com/voxpupuli/puppet-telegraf/pull/190

Hello, would anyone have time to review this PR? I think that would be a good addition for that module and any that use it as a dependency https://github.com/voxpupuli/puppet-telegraf/pull/190

merging heira and pe class params.. you can argue if that's 'legit' or not.

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

Well that's a learning moment... squash BEFORE marking it for approval again 🙂

and can I get a review for https://github.com/voxpupuli/modulesync_config/pull/792 ?

yop puppetdb-ruby not work on ruby > 3.0 ?

possible. you can submit a PR for it if you like 🙂

Is there voxpupuli automation for github repo branch protection and creating the standard set of PR labels?

we usually don't have a branch protection. For labels, we are working on https://github.com/voxpupuli/vox-pupuli-tasks/ , which will correct/configure labels

we usually don't have a branch protection. For labels, we are working on https://github.com/voxpupuli/vox-pupuli-tasks/ , which will correct/configure labels

Does the Vox tooling allow for a

spec_helper_local.rb

?

Hi folks, stuck on the migration of

augeasproviders_ssh

into the more regular vox way of doing things. Created a comment in the draft PR with details (also not sure why the test is failing since it's a copy from

augeasproviders_pam

).

@tvaughan I don't see a

.sync.yml

file. Did you run modulesync?

@jhoblitt I didn't. I'm trying to make as few changes as possible at the moment. Might be too far gone for that though 😄