An elegant way to see if a given host has 40G or more link speed in total would also be great (so hiera could load my big network tunings yaml)

Hi folks, Have a question about open source puppet, ask away!

yes! Will the Puppet 6 EoL date be shifted until Puppet 8 is released?

This message was deleted.

This message was deleted.

@David Sandilands ^

This message was deleted.

@josh, I have random failures of hiera-eyaml-gpg after migrating to PE2021. The gem is discarding errors, unfortunately https://github.com/voxpupuli/hiera-eyaml-gpg/blob/master/lib/hiera/backend/eyaml/encryptors/gpg/puppet_gpg.rb#L18 Looking at Puppet:Util:Execution.execute, it seems I don't have a good option to collect stderr. Is there another method that can be used?

This message was deleted.

puppetserver injects its

Puppet::Util::Execution.execute

implementation which ultimately calls into clojure. I would expect the stderr output to be logged to puppetserver's log based on https://github.com/puppetlabs/clj-shell-utils/blob/bf95a25bcd8865c7770f26188b0f25ba9aee0b76/src/java/com/puppetlabs/puppetserver/ShellUtils.java#L100-L102

Is anyone running with

strict_variables=true

and

strict=error

with puppetserver 7? If so, how are you interpolating fact and/or node parameters in your

hiera.yaml

, e.g.

hierarchy:
  - name: "roles"
    path: "roles/%{role}.yaml"

I do!

even on puppet 6

This message was deleted.

The reason I ask is we've uncovered some not well-defined behavior if the hierarchy is defined using top-level variables. Puppet loads

hiera.yaml

and attempts to create the various data providers. But since this happens outside of any compilation, it will raise (when

strict/strict_variables

is set to error)

Maybe something like `strace -f -e trace=exec -p `pgrep java`` Also check that the

pe-puppet

user has read permission to

/tmp/puppet-eyaml-hiera-gpg-input20230215-129448-8gat21

Also maybe selinux?

The reason I ask is we've uncovered some not well-defined behavior if the hierarchy is defined using top-level variables, eg like facts or node parameters. Puppet loads

hiera.yaml

and attempts to create the various data providers. But since this happens outside of any compilation, it will raise (when

strict/strict_variables

is set to error)

Is anyone running with

strict_variables=true

and

strict=error

with puppetserver 7? If so, how are you interpolating fact and/or node parameters in your

hiera.yaml

, e.g.

hierarchy:
  - name: "roles"
    path: "roles/%{roles}.yaml"

Is anyone running with

strict_variables=true

and

strict=error

with puppetserver 7? If so, how are you interpolating fact and/or node parameters in your

hiera.yaml

, e.g.

hierarchy:
  - name: "roles"
    path: "roles/%{role}.yaml"

@josh can you please check this thread in #C0W298S9G? I was recommended to ask you about it during an office-hours day https://puppetcommunity.slack.com/archives/C0W298S9G/p1677263313600889 The problem I'm having is described at the beginning of the thread, with a better example later in the thread: https://puppetcommunity.slack.com/archives/C0W298S9G/p1677272492698269?thread_ts=1677263313.600889&cid=C0W298S9G

goodnews Next up is 🧑‍🏫 Bolt in 4 hours

Alright folks, that's a wrap for today, see you in two weeks!

This message was deleted.

letsplay 🧑‍🏫 Bolt is about to start up in 15 minutes

Hi there. Planning on doing a bolt release tomorrow with some minor fixes

o/

Any chance to merge my PR that add support for FreeBSD jails transport? 😁

ah, that one...

I'll take a look, I recall Nick was looking at that with you too. I'll see if he has any additional concerns

Cool, thanks! It has been sitting for a while, and I realize that the "Conversation" tab is barely lisible because I used the PR number in the commit messages. If the time does not permit to merge it, I can cherry-pick the commit in the FreeBSD packages, but I would prefer to limit the amount of patches we have to maintain 😉