heyho dear humans - I have added a basic module for opensearch at https://github.com/voxpupuli/puppet-opensearch - it is really basic - and there are still some example missing - also the readme is still the one from pdk init.

Is it very different from the elasticsearch? Maybe it’s better to enhance the elasticsearch module with “flavours”?

Do you mean enhancing the elasticsearch module?

No no no no - never ! 😄

the vox postfix module, it's been recently updated so looks well maintained, it doesn't seem to support TLS in the postfix configuration options, which seems a pretty big gap for a modern MTA, am I correct or have I missed it in the documentation

I don't use it myself, but if you missed it and it's there, then that's at least something worth of a PR :)

if it's not there - it's worth a PR

but going through it, I don't see anything that supports any of the config options needed, eg: certification name / location, listening port etc

I've never looked at the source myself, so you may be right - I just don't know :)

it's only the fact that it feels a basic modern requirement for an MTA that's making me doubt it, it seems like such a big but basic function to overlook

I just add in a profile what's missing, it's mostly opinionated

postfix::config {
    'smtp_use_tls':
      value => 'yes',
      ;
    'smtp_tls_CAfile':
      value => '/etc/ssl/certs/ca-bundle.crt',
      ;
  }

how are you doing that ??

example above

sorry, I mean they are not valid parameters

hmm. works for me

ahhh I see it now

so they are not valid configs, but you can pass in options are values

right, you can add configuration blocks

so in theory you could do config { 'smelly_smell_smell': value => true ] and it would set a parameter called smelly_smell_smell

I see how it's doing it now, that's simple and clever at the same time

thank you, I'd not seen that as I was looking for the parameters and the template config too much

I agree with your though. having a postfix:profile:mta with standard configuration would be useful

in your example could you pass in those parameters with hiera ?

I'm assuming you could do something post postfix:configsmtp use tls true

you don't, you need a profile class that will translate those

ahhhhhh so it needs the profile, ok the header in config.pp didn't say that,

let me check the code, I could be wrong

no, I think you're right, looking at the examples they are all in a profile format

that can't be an accident 😉

Nope you can -

# @param configs
#   A hash of postfix::config resources. The hash containing optional configuration values for <http://main.cf|main.cf>.
#   The values are configured using postfix::config.
#   Example: `{'message_size_limit': {'value': '51200000'}}`
#