you would have to make specific file for each companyid/datacenter combination, that's why I think template would be better

and it would go under templates/ folder

puppet would never look for files under manifests/ and vice versa

I appreciate the response... so in my head.. I want to have multiple base.pp profiles one for Linux and one for Windows ..etc . I know there are better ways to do this all from a single base.pp but in my head I would organize that profile along with its corresponding linux specific config files within its own sub-class (probably wrong term) ... we will have lots of linux specific profiles as ..etc in the future and I was just trying to plan ahead with organization or things...

profile::linux::base

made sense to me.. and maybe down the road:

profile::windows::base

all profiles for linux go into:

profile::linux

^^ these are subclasses yes? they would go into the

$env/site-modules/profile/manifests

?

correct, but each

::

there would represent additional directory level

so

profile::linux

class is in profile/manifests/linux.pp

profile::linux::base

class in profile/manifests/linux/base.pp

and so on

and that is quite acceptable structure you can have class

profile::base

for example (profile/manifests/base.pp)

case $facts['kernel'] {
      'Linux'   : { contain profile::linux::base }
      'Windows' : { contain profile::windows::base }
      default   : { fail("${facts['kernel']} is not supported") }
    }

but files that you will deploy on those platforms should go to profile/files/linux/ and profiles/files/windows/

ok.. that is the disconenct

hmmm

mind blown

heheh

well, if you want to have all platform files 'together' you can create separate classes for windows and linux and have it this way

What is not intuitive with that... is in my head

profile::linux::base

the "linux" is just as much a module as "profile" and would have its own relative file dir ?

only first component is a module

ah ok..

then why would "Linux" have a manifests dir? that is very module'y 🙂

it only does in your environment 😉

but if you call your module linux, you will have linux/manifests/

and class linux will be in linux/manifests/init.pp

ok I think I follow 😛

I so appreciate you helping me process this

There will be a day when it all clicks in my head... 😄

There will be a day when it all clicks in my head... 😄

yep. it's pretty logical

I've found that puppet is a huge exercise in taxonomy and the pain comes from we don't always think about things in a strictly first filter/second filter way (e.g. first filter might be os, second filter might be web server but sometimes we flip them the other way). mapping those buckets onto puppet code is always a treat and everyone organizes things slightly differently. Eventually it does click though.

hello all, looking at the supported OS page for server installation and rocky linux, I only see Rocky 8 (EL8)... however Rocky 9 (EL9) agents are supported. Is there any plan for EL 9 support any time soon maybe?