bastelfreak: just waiting on CI

"No binary rubies available for: oracle/8/x86_64/ruby-2.6.5" …

lol

that's new

and "No binary rubies available for: oracle/8/x86_64/ruby-2.7.0" too

and then CI fails because we don't install all the compile tools to build one

lovely

just remove it from metadata.json?

was going to be my suggestion

a good stress test for the GH UI

:D

yes

mhm spec tests don't like me

mhm if someone has an idea about https://github.com/voxpupuli/facterdb/pull/298 please let me know

Hey there, I have a question regarding the stdlib deprecations pre 9.0 and I hope I’m in the right channel. The problem is, that we don’t see the deprecations warnings. We added

STDLIB_LOG_DEPRECATIONS=true

to the Puppet server as well as the agent but no deprecations come up, neither in the puppetserver log nor in the agent log. Only if we comment out the conditional for the env variable in

lib/puppet/parser/functions/deprecation.rb

we see the deprecations. Does anybody have an idea what could be wrong here? We’re currently in the process of migrating our (component) modules to stdlib >=9. Thanks!

https://github.com/puppetlabs/puppetlabs-stdlib/blob/v8.6.0/lib/puppet/parser/functions/deprecation.rb#L18 the parse error should always be logged to puppetserver.log

GH HTTP 500 time again, so lunch time

@bastelfreak Parse Error? No, I meant the deprecation warning starting with the conditional in this line: https://github.com/puppetlabs/puppetlabs-stdlib/blob/v8.6.0/lib/puppet/parser/functions/deprecation.rb#L23

This conditional is never true in our case for whatever reason…

ah I confused myself

https://github.com/puppetlabs/puppetlabs-stdlib/blob/v8.6.0/lib/puppet/functions/deprecation.rb that's the file I had in mind and that logs to puppetserver.log by default

Yeah, interestingly enough, that file isn’t even reached on our side (tested with raise-commands in the file), our deprecations are only logged by the parser/functions function. Which is odd to me because THOSE functions are pre Puppet4 function implementations, right?

which specific function do you have in your puppet code that doesn't trigger a deprecation?

validate_re for example.

But also validate_bool, etc. In fact I’m migrating the old AEM module by bstopp: https://github.com/dodevops/puppet-aem/tree/main

e.g. this call: https://github.com/dodevops/puppet-aem/blob/main/manifests/instance.pp#L33

https://github.com/puppetlabs/puppetlabs-stdlib/blob/v8.6.0/lib/puppet/functions/validate_re.rb this call this: https://github.com/puppetlabs/puppetlabs-stdlib/blob/v8.6.0/lib/puppet/functions/deprecation.rb

Do you have

strict

configured on the puppetserver?