Puppet Community

If I set it to true inline the catalog does not compile

```pdk new module
cd bugtest
pdk new class bugtest```
init.pp:
```class bugtest {
  package { 'rsyslog':
    ensure =&gt; latest,
  }

  class { 'freeradius':
    ldap_support    =&gt; true,
    syslog          =&gt; false,
    log_destination =&gt; 'syslog',
    log_auth        =&gt; 'yes',
    utils_support   =&gt; true,
  }
}```
.fixtures.yaml:
```---
fixtures:
  repositories:
    stdlib: "<https://github.com/puppetlabs/puppetlabs-stdlib.git>"
    concat: "<https://github.com/puppetlabs/puppetlabs-concat.git>"
    rsyslog:
      repo: "<https://github.com/saz/puppet-rsyslog.git>"
      ref: "v5.0.0"
    freeradius: "<https://github.com/djjudas21/puppet-freeradius>"
    logrotate:
      repo: "<https://github.com/voxpupuli/puppet-logrotate>"
      ref: "v7.0.1"```
common.yaml
```---
freeradius::syslog: true```

expected behavior:
The catalog should not compile

observed behavior:
The catalog compiles

If you comment out the yaml, and just set `syslog =&gt; true` manually on the freeradius class, the catalog does not compile, as expected

the freeradius module adds a `rsyslog::snippet` resource if `syslog` is true. That resource includes the main `rsyslog` class, which includes an `install.pp` class that declares the package

So It is not supposed to compile when `syslog` is true

in which common.yaml did you add that parameter? in the bugtest module?

the bugtest module is completely isolated right now

We dont even have a file with that name in controlrepo

when you use the module layer for hiera, you can only set parameters for this module

so `freeradius::syslog: true` works only in the `freeradius` module

thats a mistake in this test then, is there any way to get hiera working in the module

Hiera in the module works, but you cannot use it to set data for another module

So there's no way to add it to hiera like it would be in a controlrepo?

to come back to your initial error; rspec-puppet ignores your hiera data because the hiera data is for the wrong module?

No
There is a second layer bug in the controlrepo that I was not able to reproduce in the test, and this hiera business explains that part

In the controlrepo, `freeradius::syslog: true` is set in a node specific yaml file, while `syslog        =&gt; false` is set in a profile.

The default in the module is also to have that be false. However:

Compiles:
`syslog =&gt; false`
`freeradius::syslog: true`

Does not compile:
`#syslog =&gt; false`
`freeradius::syslog: true`

That is, when the profile does not explicitly set the parameter to false, the yaml causes the catalog to not compile, but if the parameter is explicitly set, it does compile for some reason

I guess its possible that the puppet code gets a higher priority than the yaml? I just always assumed yaml had the final say

When you call a class and provide an explicit value, puppet won't do any hiera lookup for that parameter

Is there a doc somewhere I can review to get more familiar with this?

It's probably somewhere here <https://www.puppet.com/docs/puppet/8/hiera_intro.html|https://www.puppet.com/docs/puppet/8/hiera_intro.html>

Doesn't seem to mention it, altho the more I think about it, it's actually kind of intuitive

`Earlier data sources have priority over later ones`
If you consider puppet code as a pseudo layer 0, makes good sense!

*I* have an <https://github.com/bschonec/puppet-s390utils-cpuplugd|s390 module> that I wrote long ago that is no longer useful to me.  If there's anyone out there that uses s390 and 'cpuplugd' I'd be willing to donate my module to the community -- if there's interest.

It works but it's nowhere near the quality that it should be.

what are you all doing for postgres/mariadb instance creation / management, especially replication

what modules/hacks are you using with puppet

best tip for mariadb ist to replace it with postgres

not used patroni before, I was more talking about modules

there's a patroni module as well, from <@U2PU8Q22G>

want to try to bring my postgres deployments (and maria - sorry) into alignment

if streaming replication is enough, that's built into postgres itself

<https://github.com/hapostgres/pg_auto_failover> that also works well

how do you find managing PG instances with puppet, I've not really done much with it before beyond the package installation and config parameters

For clusters, it depends. They usually have their own cluster manager that enforces state. So you need to check what it does and use puppet for the rest

I'm playing with the puppetlabs module at the moment

Is this valid syntax?
```if /^hostname-(1|2|3)/ in $trusted['certname'] { ... }```

```if $trusted['certname'] =~ /^hostname-(1|2|3)/ {```