at least according to the ERB template.. maybe we can drop some variants though..

I see no nested hashes in the unit tests but I see this in the original ERB

https://github.com/voxpupuli/beaker-hostgenerator/pull/313 I took a stab at further reducing the size of the file data.rb

just curious if anyone saw a config which uses this in

*_cfg_{append,prepend}

in nginx: https://github.com/voxpupuli/puppet-nginx/blob/master/templates/mailhost/mailhost.erb#L8

I mean exactly the case when it’s Hash[String, Hash[String, Array[String]]]

I cannot imagine in which case in nginx.conf this can be useful..

well.. found it can be used within upstream maybe:

upstream big_server_com {
    server 127.0.0.3:8000 weight=5;
    server 127.0.0.3:8001 weight=5;
    server 192.168.0.1:8000;
    server 192.168.0.1:8001;
  }

so

{ 'server' => { '127.0.0.3:8000' => 'weight=3' }}

.. 😱

I just want it to be Array[String] and that’s it please..

well.. I guess this batch if ready finally: https://github.com/voxpupuli/puppet-nginx/pull/1568

had a look over the puppet-nginx issues and found some complaints regarding the

*_cfg_{append,prepend}

parameters behaviour 😞

See the

puppet-nginx

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

ewoud: I saw you switched ‘{ ’ to ' {' when finalising an

if

line.. not sure what was the reason but now it produces double space before the

{

and no space after:

<% if $default  {%>

VoxBot: hmm, interesting because when I tried to use it in a test it showed up in a weird way

ah.. I didn’t tried unit tests there yet.. maybe that’s why it’s unclear for me

Hallochen Vox! hattip ☕ Most of you know this already from our Vox sync last week, but here we go! This is just a reminder of the upcoming maintenance on the Forge this Wednesday 👇 https://puppetcommunity.slack.com/archives/C0W298S9G/p1689068073536019 Thanks!

Got a tiny PR for facter 3 compat on falco https://github.com/voxpupuli/puppet-falco/pull/31

Hunner: as a ruby non-expert, why do those braces make a difference?

The original result from the command util resolution is passed directly to the

confine

function, and the curly braces turn that into a block (similar to

do...end

) that can be executed differently

Puppet 7 and facter 4 seem to handle non-block confines, but puppet 6 and facter 3 stil needs blocks

ah I see, hmm, thanks

there's probably also a difference that a non-block is executed greedy (so when the file is loaded) while a block is loaded lazily (when block.call is invoked)

so I suspect that if you run facter os it will never call the block when you use confine { … } but confine … will run

ewoud: ohhh quite a good point

The non-block version would show issues when the command becomes available but a persistent puppet agent isn't restarted. Anyway, I wonder why facter 4 didn't also throw an error when no block is supplied? Seems like something that should be an issue and not an intended behavior

Hi all! Do this result from yum module GitHub merge hook indicate the problem is indeed the outdated

REFERENCE.md

file? If so, how can I get details on the file problem - in other words, to know what exactly is outdated?

@emerson_prado

REFERENCE.md

is generated by

bundle exec rake reference

bundle exec rake reference
  The "reference" task is deprecated.

  Prefer "release:prepare" which manage all pre-release steps, or directly run
  the "strings:generate:reference" task.

Should I run

bundle exec rake strings:generate:reference

?

ah yeah, thought that was the case, I was in the process of checking

@kenyon Fixed. Thanks!