This message was deleted.

See the

simp-krb5

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

Hello Everyone, I'm Ram from India and I work as a full-time community person for open source. I came across Puppet recently and I am finding it really interesting. While I am using it and getting more knowledge on the tech side, if there are any kinds of non-code contributions that I can make, I'd be happy to help.

A recent update to puppetlabs-apache added parameter type validation to apache::custom_config, which breaks something for us. Some of our custom configs contain secrets (we put okta secrets into it, for instance). Would it be an option to just change

Optional[String] $content             = undef,

to

Optional[Variant[String],Sensitive[String]] $content             = undef,

or am I missint something obvious?

See the

puppetlabs-apache

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

A recent update to puppetlabs-apache added parameter type validation to apache::custom_config, which breaks something for us. Some of our custom configs contain secrets (we put okta secrets into it, for instance. Would it be an option to just change

Optional[String] $content             = undef,

to

Optional[Variant[String],Sensitive[String]] $content             = undef,

or am I missint something obvious?

A recent update to puppetlabs-apache added parameter type validation to apache::custom_config, which breaks something for us. Some of our custom configs contain secrets (we put okta secrets into it, for instance). Would it be an option to just change

Optional[String] $content             = undef,

to

Optional[Variant[String],Sensitive[String]] $content             = undef,

or am I missint something obvious?

If someone could push

v1.1.5

of

puppetlabs/patching_as_code

to the Forge, that would be very much appreciated! Just kick the “Manual push to Forge” job in the internal jenkins, providing this model name and tag, and it will do the rest for you :-)

See the

puppetlabs-patching_as_code

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

@Carmen Sze has left the channel

This message was deleted.

Which ever one is supported/vetted by Puppet Inc and gives the best performance.

hey folks, probably a silly question, but just found that running

puppetserver ca clean --certname <fqdn>

is timing out, was poking around and the only thing i found was this on our CA

wc -l inventory.txt       
353826 inventory.txt

is there a “correct” way to clean this file up? we tend to run < 1000 instances at a time. I suspect that the clean process is having an issue reading the file but can append to it no problem

hey folks, probably a silly question, but just found that running

puppetserver ca clean --certname <fqdn>

is timing out, was poking around and the only thing i found was this on our CA

wc -l inventory.txt       
353826 inventory.txt

is there a “correct” way to clean this file up? we tend to run < 1000 instances at a time. I suspect that the clean process is having an issue reading the file but can append to it no problem

and if this is the wrong place to ask, if someone could point in the correct direction, that would be appreciated

this is the right place to ask

I'd look for a config setting for the timeout

you should also see an entry for the failure in the puppetserver.log

right, but is it necessary to keep all inventory dating back a couple years?

do you not clean certs as part of your decom process?

we do

I think you can stop the puppetserver, clean the file, restart it

long story short, we do, but we have so much autoscaling that sometimes instances get skipped for whatever reason so we end up with stragglers that end up accumulating over time

@bastelfreak let me give that a shot, thanks!

make a backup

just mv it away

yup, was about to do that

yeah, it did not like that

why not?

failed to start, looking at logs