Ah, here's that plugin I was thinking of: https://github.com/voxpupuli/puppet-lint-optional_default-check Its readme explains why the check is needed.

Ah, here's that plugin I was thinking of: https://github.com/voxpupuli/puppet-lint-optional_default-check It's readme explains why the check is needed.

that is what I was looking for, so param is required, a default is commonly used, but non-defaults have a strict list of acceptable values

Ah, here's that plugin I was thinking of: https://github.com/voxpupuli/puppet-lint-optional_default-check Its readme explains why the check is needed.

We wrote some guidelines about parameters/datatypes at https://voxpupuli.org/docs/reviewing_pr/

There's a puppet-lint plugin that checks for that (I'm not sure if that's a core check or not). So if you want the parameter to default to

'thing1'

, for example, I'd make the parameter definition be:

Enum['thing1', 'thing2'] $param = 'thing1'

Trying to refresh a possibly misplaced memory but, isn't there a command to add to "puppet agent -t" when you're running a feature branch into dev? Otherwise, when I run "puppet agent -t" it removes my feature files.

--environment <X>

?

where

<X>

is the branch you want to use?

That does seem not only reasonable and makes sense. I'll give it a go.

Real hard hitting, difficult question for you folks today. What word do you use for Puppet code that conforms to best Puppet practice? (like the word Pythonic for Python)

This message was deleted.

Hi everyone ! Does anyone know where I can find a quite complex example of what a Puppet code base would look like ? (Like.. What the

code/environments/production

folder would like for a complex architecture) Thanks for your help!

This message was deleted.

@redat The Wikimedia Puppet repo is a good example of a very active and very real, production code base: https://github.com/wikimedia/puppet

This message was deleted.

This message was deleted.

Yep, I just answered my own question as I was writing it lol. Tried again using the genuine hostname as the certname and adding the cnames to the san and that seems to have worked. Thanks

Hello according https://stackoverflow.com/questions/19013084/in-puppet-how-can-i-access-a-variable-attribute-inside-a-defined-type

It doesn't seem that you can access a defined type's attributes.

do you know if it still apply (its from 8 years ago 😞 )

This message was deleted.

message has been deleted

Can you maybe achive this one on filesystem basis like using

.d/*

definitions?

Or try this to get from the hiera level. You can collect all keys of an hash that created your

consul::configs

This message was deleted.

I feel like this was asked here before but I can't find it anywhere. Running puppet ssl bootstrap on an agent node appends a "dot" to the end of the cert,

server01..pem

- I don't control the network this server resized in, I'm assuming this is a byproduct of said network. is there a way around this? That dot is causing issues with the post request to the master.

Debug: HTTP PUT <https://puppet:8140/puppet-ca/v1/certificate_request/server01>. returned 400 Bad Request

I feel like this was asked here before but I can't find it anywhere. Running puppet ssl bootstrap on an agent node appends a "dot" to the end of the cert,

server01..pem

- I don't control the network this server resides in, I'm assuming this is a byproduct of said network. is there a way around this? That dot is causing issues with the post request to the master.

Debug: HTTP PUT <https://puppet:8140/puppet-ca/v1/certificate_request/server01>. returned 400 Bad Request

At the risk of exposing my lack of skills once again: I'm trying to set up some local spec testing on a RHEL8 system. I'm using puppet-cron module and have (I think) installed the necessary stuff for spec testing. I typed "rake spec" and I expected something to happen but "rake spec" returned almost immediately with no output. I tried doing "pdk test" (or something like that) and it barked at me about upgrading the spec test files (which I did) and then the tests ran -- mostly successfully -- after about 40 seconds. Is "rake spec" the command I should be using? I'm coming at this with zero experience with testing and I need to be able to do the testing via a Jenkins pipeline. I don't understand why or what I'm doing yet and I'd just like to get tests kicked off even though I can't write any tests for myself yet. All I want to do for now is to get a linux server running to do the tests. Any advice is appreciated.

See the

puppet-cron

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

At the risk of exposing my lack of skills once again: I'm trying to set up some local spec testing on a RHEL8 system. I'm using puppet-cron module and have (I think) installed the necessary stuff for spec testing. I typed "rake spec" and I expected something to happen but "rake spec" returned almost immediately with no output. I tried doing "pdk test" (or something like that) and it barked at me about upgrading the spec test files (which I did) and then the tests ran -- mostly successfully -- after about 40 seconds. Is "rake spec" the command I should be using? I'm coming at this with zero experience with testing and I need to be able to do the testing via a Jenkins pipeline. I don't understand why or what I'm doing yet and I'd just like to get tests kicked off even though I can't write any tests for myself yet. All I want to do for now is to get a linux server running to do the tests. Any advice is appreciated.

if you're using pdk already, I would use pdk validate and pdk test unit