This message was deleted.

port is Integer, not a String nowadays

this notation is preferred

include apache::mod::alias

class { 'apache::mod::alias': }

this notation is preferred

include apache::mod::alias

not

class { 'apache::mod::alias': }

Would something like provisioning user accounts and SSH key pairs be done viaa profile that references a module/class opposed to as a mod ?

Would something like provisioning user accounts and SSH key pairs be done viaa profile that references a module/class opposed to as a mod ?

or just via hiera

https://forge.puppet.com/modules/puppetlabs/accounts shows some good examples of both options

yep, use the accounts module

Thanks, trying to think of a scalable method of deploying the user resouce type.

Examples I found via google specified creating a discrete module and init PP for a single user account.. but that doesn't exactly scale imo

Examples I found via google specified creating a discrete module and init PP for a single user account.. but that doesn't exactly scale imo

This message was deleted.

This message was deleted.

That's assuming our linux servers are kerberos bound =P

but good point, just manage the membership in that case

I really should KRB join my homelab servers atleast.

message has been deleted

nevermind, I just answered my own question. https://github.com/voxpupuli/hiera-eyaml

message has been deleted

Anyone know of a replacement module for the puppet_certificate module on the forge ? It is not compatible with Puppet 7 but we need the functionality it provides - letting an agent clean/request their own certificates.

Soooo, This isn't really directly puppet related but what is standard practice for web servers that have library dependencies? I got a request to dirtily clone like 10 prod web servers for test/dev purposes. Aside from having to schedule time to take the prod servers offline, this also has a bunch of work where one has to manually change their names, IP ADDR, Agent GUID change/reinstall, etc.

It gets a bit murky as the person requesting it is in a different team, but I'm not really sure if there is a standard practice for this? I'd feel that it's a lot easier to provision those servers using puppet and then just have a test/dev/prod branch. I can certainly make reccomendations but don't really have anything in my hands stating what best practice is.

It gets a bit murky as the person requesting it is in a different team, but I'm not really sure if there is a standard practice for this? I'd feel that it's a lot easier to provision those servers using puppet and then just have a test/dev/prod branch. I can certainly make reccomendations but don't really have anything in my hands stating what best practice is.

yep. provision new systems, manage their state with Puppet

We keep getting requests to clone X web server every few months so they can test an OS/Product/Library update

Whereas it should be as simple as nuking that existing test/dev server, merging the prod branch onto the test one and then provisioning that new test server with the profile applied to it.

Whereas it should be as simple as nuking that existing test/dev server, merging the prod branch onto the test one and then provisioning that new test server with the profile applied to it.

something like that, yes