what's up with the puppet debian repositories today?

if their location has anything at all to do with Comcast or Comcast properties, they’re likely offline. Massive outage underway.

for the record, https://apt.puppetlabs.com/ works for me

Has anyone ever seen this kind of error when trying to execute pdk commands?

/opt/rh/rh-ruby27/root/usr/share/gems/gems/psych-3.1.0/lib/psych.rb:233: warning: already initialized constant Psych::LIBYAML_VERSION
/opt/rh/rh-ruby27/root/usr/share/ruby/psych.rb:233: warning: previous definition of LIBYAML_VERSION was here
/opt/rh/rh-ruby27/root/usr/share/gems/gems/psych-3.1.0/lib/psych.rb:235: warning: already initialized constant Psych::NOT_GIVEN
/opt/rh/rh-ruby27/root/usr/share/ruby/psych.rb:235: warning: previous definition of NOT_GIVEN was here
pdk (INFO): Using Ruby 2.7.4
pdk (INFO): Using Puppet 6.28.0
/opt/rh/rh-ruby27/root/usr/share/rubygems/rubygems.rb:277:in `find_spec_for_exe': can't find gem bundler (>= 0.a) with executable bundle (Gem::GemNotFoundException)
	from /opt/rh/rh-ruby27/root/usr/share/rubygems/rubygems.rb:296:in `activate_bin_path'
	from /opt/rh/rh-ruby27/root/usr/bin/bundle:23:in `<main>'

For context, this is using the pdk gem in a Ruby 2.7 software collection install inside of a docker image that's installed at runtime by a non-root user on a centos 7 based image (running inside of a gitlabci pipeline). My initial googling found this bit of wisdom, but it claims that Ruby 2.6.3 should effectively solve this issue, but as you can see in the logs, we're past that version.

This message was deleted.

There are two tickets in puppet’s Jira about this with various options. I implemented one of the options - a puppet language hiera data backend. It is in my “tahu” module: https://github.com/hlindberg/tahu/blob/master/lib/puppet/functions/tahu/ppyaml_key.rb With it you would have a data file like

the::key: "{ 'password' => Sensitive('fish happy universe')}"

And for lookup of

the::key

you would get a Hash with one Sensitive value for the key

password

. If you set up your hiera to do deep_merge for those keys it would be enough to have all the sensitive keys in a separate data file with higher prio in the hierarchy.

This message was deleted.

This message was deleted.

This message was deleted.

Day 7 https://adventofcode.com/2022/day/7. Who is participating is sharing the code in this discussion https://github.com/puppetlabs/community/discussions/28 (but slack is fine too) and there are lots of neat snippets that show how some less used functions could be used.

Day 7 https://adventofcode.com/2022/day/7. Who is participating is sharing the code in this discussion https://github.com/puppetlabs/community/discussions/28 (but slack is fine too) and there are lots of neat snippets that show how some less used functions could be used.

Here's a link to the mailing list announcement for those that aren't subscribed to puppet-dev: https://groups.google.com/g/puppet-dev/c/0ObKV0cpLDY/m/X2vcB2bbAAAJ Unfortunately it's not currently possible to run puppet from source or as a gem against Ruby 3.2 preview releases due to breaking changes in Ruby. Hopefully that should be resolved soon https://tickets.puppetlabs.com/browse/PUP-11634

This message was deleted.

Thanks everyone, your help is much appreciated. I just tried manually installing mysql-server from apt on a clean 20.04 image and the service immediately fails to start. Something weird going on

Really dumb question but how do you list all nodes on puppet 7? I can’t find this anywhere. With puppet 5 you could run

puppet cert list --all

, but

puppet cert

isn’t available any more I found

puppetserver ca list --all

but that shows nodes that aren’t currently connected

puppetserver ca list

shows certificate requests;

--all

will show signed certs as well which is similar to the behaviour of the legacy cert list --all (https://puppet.com/docs/puppet/5.5/man/cert.html) ref: https://puppet.com/docs/puppet/7/subcommands.html#ca

I'm trying to use

puppet/splunk

module. i'm looking to puppetize some Splunk heavy forwarders how when I run

puppet resource splunk_output

it comes back with

file_path must be set with splunkenterprise_config or splunkforwarder_config type before provider can be used

cant find where

splunkenterprise_config

in the code base

See the

puppet-splunk

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

This message was deleted.

See the

puppetlabs-puppetdb

module at https://forge.puppet.com/puppetlabs/puppetdb?src=slack&channel=puppet

fry dancing 🧑‍🏫Puppet Forge is about to start up in #CFD8Z9A4T

hi everyone, I was wandering if anyone had issues with hiera lookup command vs function conflicting results maybe and how to troubleshoot those? I have in

hiera.yaml

- name: 'internal_lb glob'
    data_hash: yaml_data
    globs:
      - "%{brand}/backend_lb/rules/%{deployment_tier}/%{datacenter}/internal_lb*.yaml"
      - "%{brand}/backend_lb/monitors/%{deployment_tier}/%{datacenter}/internal_lb*.yaml"
      - "%{brand}/backend_lb/pools/%{deployment_tier}/%{datacenter}/internal_lb*.yaml"
      - "%{brand}/backend_lb/vips/%{deployment_tier}/%{datacenter}/internal_lb*.yaml"
      - "%{brand}/backend_lb/params/%{deployment_tier}/%{datacenter}/internal_lb*.yaml"

and I have those in place in my data folder. When performing lookup command like:

puppet lookup profile::component::internal_lb --merge deep --environment production --node some-server-01.local

I get full hash displayed (and if use --debug I get the exact hiera file where it's coming from). However if I do in code:

lookup('profile::component::internal_lb', Hash, { 'strategy' => 'deep' }, {})

and apply it on that same node as in command (and same environemnt) I get empty hash instead 😕 Does anyone have any idea how to find troubleshoot or debug this? TY

I believe that you want

lookup('profile::component::internal_lb', Hash, 'deep', {})

it looks like you're combining lookup's 1st and 2nd definitions

or you could move Hash into the hash as

value_type

TY for the response I tried

lookup('profile::component::internal_lb', Hash, 'deep', {})

and

$vip_available = lookup('profile::component::internal_lb', [Hash], 'deep' {})

If I omit the default value

{}

I'm getting:

Function lookup() did not find a value for the name 'profile::component::internal_lb' on node

but puppet lookup command still works as expected.

hmmm... now this is weird... when I increased log level on puppet server I can see that when it's compiling the catalog it skips that hiera entry in

hiera.yaml

and skips emedietly to the next one:

Hierarchy entry "internal_lb glob"
          Hierarchy entry "Yaml backend"

and then it moves on resolving those paths...

when doing lookup command with --debug I can see it enters

internal_lb glob

sections and processes it regulary 🤔

You can debug by running the compilation in debug mode. Hiera will then log debug info in “explain mode”. You want to run that on a small test or you will drown in info.

ha, you already started doing that.