@johan o/

Could we get a new release tag and a new gem pushed for https://github.com/voxpupuli/hiera-eyaml/ ? Master works fine on Fedora 38 but v3.3.0 does not.

bastelfreak: Could we get a new release tag and a new gem pushed for https://github.com/voxpupuli/hiera-eyaml/ ? Master works fine on Fedora 38 but v3.3.0 does not.

morning

can I get a review for https://github.com/voxpupuli/beaker-module_install_helper/pull/47

halstead: I will need to do some cleanup first: https://github.com/voxpupuli/hiera-eyaml/pull/345

https://github.com/voxpupuli/hiera-eyaml/pull/347 looks good

halstead: released

Morning!

o/

Any more early opinions on https://github.com/voxpupuli/puppet-ldapquery/pull/47 ? A separate dispatch to the existing function name seemed sensible at first, but now I'm not too sure. I could just make it a new

ldapquery::search

function and leave the existing one 100% as is?? Either way, getting the API 'right' so we're not changing it again soon is important.

@straylen Did you have any preference?

ewoud: Your opinion is always valued (as it's almost always 'correct'!) :)

your* :P

I speak english good

I normally notice about 2 seconds after hitting 'enter'. I can edit slack messages, but then there's the IRC bridge, so I can't hide my sins!

IRC trained me in that way :)

I'm starting to lean a bit more towards a new function and a clean break where the old one doesn't call the new one but I just leave it untouched to die (remove in a much later release). I recently added https://github.com/voxpupuli/puppet-ldapquery/pull/47/commits/47d523c946109556cc5650c0e1eaea3679dc3fbe and whilst I think this is a sensible approach it'll change the behaviour of the existing function/dispatch.

The current function will explode over things like connection refused, but return an empty result set for other things such as invalid auth.

but I'm working on translations today and it's my last day before my vacation, so can't really be distracted now

I also don't want to have a single breaking release where I replace one implementation with the other. This can be a real blocker to some people upgrading. Imagine a case where several different teams use the function in different modules/profiles they 'own'. Coordinating everyone to update at the same time isn't always practical.

ewoud: any plans to migrate https://github.com/ekohl/metadata_json_deps to vox pupuli?

bastelfreak: not yet, but I could look into that

mhm

See the

theforeman-motd

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

where is the 1.0.0 coming from

puppet forge