Puppet Community

yeah that's more of a major change I think

I am pretty sure that el's .bashrc/.bash_profile has a direct call to include /etc/profile

one day someone (Poettering?) will rewrite all this mess..

the person will be as hated as Poettering though.. :slightly_smiling_face:

in before someone writes a ruby configuration language for shell

yeah.. need another xonsh but in ruby :slightly_smiling_face:

the second one would be almost useful for an irb session

there are different tests:
• unit tests for ruby and puppet code (rspec, puppet-rspec)
• acceptance tests for a module behaviour (beaker)

PDK allows you to do unit tests easily (as well as overall validation)

acceptance tests may need some more work because such test is actually applying your module and checking it works in reality

I learnt things by reading other tests and trying to implement what I’d like to do.. rspec-puppet is simplest, rspec for ruby code may need some specific googling/RTFM-ing

acceptance tests with beaker may need some source reading too sometimes :smile:

yeah acceptance tests are a different beast, I guess I'll leave that for later.

I have two goals here, one would be to learn the basics, the other to hopefully start applying them to a large codebase that is essentially void of any sort of testing, which may be difficult to do

I can share my own module with puppet and acceptance tests enabled: <https://github.com/jay7x/puppet-vaultbot>

And there is kind of control repo with PDK and tests: <https://github.com/jay7x/puppetbolt-control_repo>

thanks for that! will definitely take a look

See the `puppet-falco` module at <https://forge.puppet.com/puppet/falco?src=slack&amp;channel=voxpupuli>

Looks like stdlib 9.x.x is out for folks who want to start thinking about mass patching various modules

systemd has done away with need for profile envs. ~/.config/environment.d gives you a shell neutral way to set stuff. Have started using it.. though have yet to find a way to reload with out logging in again.

frisbee[m]: I am happy to review your PRs for beaker to implement this :D

the thing is that beaker supports non systemd OSes as well

environment.d doesn't do what I actually need from a profile/bashrc

Going to try asking here - any ideas on how best to mark PG packages held when using puppetlabs-postgresql?  I'm not seeing the "mark =&gt; hold" option in the package resources, and the "postgresql::server::ensure" param is setup as an enum that doesn't include "held".

See the `puppetlabs-postgresql` module at <https://forge.puppet.com/puppetlabs/postgresql?src=slack&amp;channel=voxpupuli>

I'm needing to have the packages held after the initial install, and would prefer to avoid the noise that comes with marking it held outside of puppet (and ideally, not have to fork the module)

FriedBob: in case you want to patch the postgresql module I am happy to review it

bastelfreak: I'd have to do it on my own time, sadly. :(

you could otherwise pay someone to do it!

I'll have to either fork it, or do it outside of puppet and deal with the noise

Lumiere: This would be for our 18.04 / 20.04 stuff currently

But you should be able to hold it in your profile I believe 

any chance on getting <https://github.com/voxpupuli/puppet-rsyslog/pull/216> prioritized ?

systemd release   - <https://github.com/voxpupuli/puppet-systemd/pull/347>  would help me - can process it.

bastelfreak: <https://github.com/voxpupuli/puppet-r10k/pull/590>