I totally understand, we use tier instead of environment, because our puppet environments don't match a prod/staging/test/dev (they're applications) so tier is prod/staging/test/dev and the puppet server is in the tier the app nodes talk to

Hmm. I suppose I could make them re-usable. I think they're named arbitrarily.

that seems like a standardization effort worth making

This is more like a thing for rolling out new versions to a portion of our fleet at a time.

So a 'stage' is activated based on server membership and the old param values are used until they're a member of the stage.

Anything where I activate membership from within puppet code isn't going to get the benefit of hiera overrides.

So it looks like I'm going to have to go and rip out includes and do class declarations.

ah, so it's a canary type of thing

'ish' yeah.

It's partly that and partly not wanting to hammer our repos with downloads.

👋 Hello, team!

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Puppet Content and Tooling Releases Supported modules Puppet 8 support was completed with the Kubernetes module release and further deferred functions were added to modules. As one of the most used and requested modules for supported status LVM was updated to be a supported module. Supported modules added: puppetlabs-lvm (2.0.2) Supported modules released: puppetlabs-kubernetes (8.0.0) puppetlabs-tomcat (7.1.0) puppetlabs-chocolatey (8.0.0)

See the

puppetlabs-lvm

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

Can someone please update puppet documentation? https://www.puppet.com/docs/pe/2021.7/installing_nix_and_windows_agents_using_an_install_script.html#customize-install-script specifies that the settings should be added using

-s

this will no longer work, the

-s

option is no longer required and leads to shell errors.

This message was deleted.

FYI, there is #C19V5U41Z channel. In my experience, console handles it automatically, no need to do anything special, but the fix was added in some recent versions

But that was for entering sensitive parameter for plans, I am not sure you can add sensitive variable, if that's what you are looking for

quick question. Using the powershell dsc modules for computermanagementdsc or any of them in fact. It seems doing a puppet resource dsc_scheduledtask <taskname> produces an error of nil property for class. Is there something I'm missing?

Hi everyone ! Having some trouble with ERB templating.. In

suricata

configuration file, there are some syntax that conflicts with the ERB templating syntax.. For example this line.. ERB is trying to interpret the

%n

because there was previously a

<%

..

#default-log-format: "[%i] %t - (%f:%l) <%d> (%n) -- "

How can I tell ERB, for this line, to NOT interpret it, but still have it in the file ?

This message was deleted.

Will this work?

have you tried it?

not yet, fixing to. I was hoping to know if it is an issue before I commit the code to test 😄

didn't work

I'm having issues where the postgresql module is creating a password for a user, but it's not the correct password and it's stored in an md5sum value. Is there a way in puppet I can un-redact/debug my code to see what it is doing?

MD5 is a one-way hash function. It's not designed to be reversible.