doesn't look kosher, but as long as it works

well this is an internal mod for ubuntu VMs 🙂 I am lucky

ok I would like to thank all for your time and input, the code is less bad and works. It is 23:20 here so I will raise an issue tomorrow. once again thanks a lot for your assistance, it is very much appreciated.

funny enough we do have

Class['apt::update'] -> Package <| provider == 'apt' |>`

in our code base, in another module which is also declared from the same metaprofile that the filebeat module is declared. So I don't understand why the collector didn't do the trick and I had to add the require in the package resource so it depends on

Class['apt::update']

This message was deleted.

Recently the visual studio code extension for puppet was updated and it yells for every line that is not intended as expected (I presume this is puppet-lint). How do I turn off the thing in VS? I normally use 4 tabs instead of 2 because of habit (I find it better)

This message was deleted.

See the

puppetlabs-apache

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

Hi Guys I have a question regarding vhost_enable_dir in puppetlabs/apache(8.1.0) forge module. https://github.com/puppetlabs/puppetlabs-apache/blob/main/manifests/init.pp#L441 Currently we are able to set this parameter to false which disables it. Is it possible to do that in the latest module? It seems like [Stdlib::Absolutepath] is the only option currently.

You can see it set as this depending on the OS family within the default params manifest.

unless there is some special way to force literal undef?

don't set it to anything, it's undef by default

not on debian

That’s not entirely correct: vhost_enable_dir is not set on any platform. Now, it may require you to set it for the Debian family, but the setting from Puppet in their apache module in their GitHub repo has it undef. https://github.com/puppetlabs/puppetlabs-apache/blob/main/manifests/init.pp#L502 The Params are undef: https://github.com/puppetlabs/puppetlabs-apache/blob/main/manifests/params.pp#L73 and the Hieradata is unpopulated:

That’s not entirely correct: vhost_enable_dir is not set on any platform. Now, it may require you to set it for the Debian family, but the setting from Puppet in their apache module in their GitHub repo has it undef. https://github.com/puppetlabs/puppetlabs-apache/blob/main/manifests/init.pp#L502 The Params are undef: https://github.com/puppetlabs/puppetlabs-apache/blob/main/manifests/params.pp#L73 and the Hieradata is unpopulated:

https://github.com/puppetlabs/puppetlabs-apache/blob/main/data/common.yaml#L1 So, @vchepkov is absolutely correct… by default, the setting is undef. >>>>>> I stand corrected. They’ve made the change in a later line in params.pp to accommodate Debian specifically. Mea Culpa. But, “yes”, you have to tell it what directory you want it to exist in, not whether you want it on or off. I don’t know that it’s ever been Boolean. I just looked into an Apache I have running on a very old OS that is serving static HTTP circa 2017, and it was not Boolean in 2017.

https://github.com/puppetlabs/puppetlabs-apache/blob/main/data/common.yaml#L1 So, @vchepkov is absolutely correct… by default, the setting is undef. It’s up to you to change it to meet your platform.

https://github.com/puppetlabs/puppetlabs-apache/blob/main/data/common.yaml#L1 So, @vchepkov is absolutely correct… by default, the setting is undef. >>>>>> I stand corrected. They’ve made the change in a later line in params.pp to accommodate Debian specifically. Mea Culpa. But, “yes”, you have to tell it what directory you want it to exist in, not whether you want it on or off. I don’t know that it’s ever been Boolean. I just looked into an Apache I have running on a very old OS that is serving static HTTP circa 2017, and it was not Boolean in 2017.

however, it type was never enforced before

so sending false as the value made https://github.com/puppetlabs/puppetlabs-apache/blob/main/manifests/init.pp#L706 not manage the file at all

so sending false as the value made https://github.com/puppetlabs/puppetlabs-apache/blob/main/manifests/init.pp#L706 not manage the file at all

Submit a fix

This message was deleted.

anyone use Prometheus

puppetdb_sd_config

? Is this a good approach for service discovery? what is kind of nice is you can use a query and find only endpoints that say have the package or class present. I don't always love creating dependencies, because it creates a much larger testing scope (ie if puppetdb goes offline, what happens, etc)

PR submitted https://github.com/puppetlabs/puppetlabs-apache/pull/2304

type should be

Optional[Variant[Stdlib::Absolutepath,Boolean[False]]]

is this kind of thing possible? passing a list of classes to require to the puppet class from hiera?

hiera:
mm::drs::trigger_jenkins::trigger_jenkins_require: 
  - Class['mm::common']

class:
  exec { 'trigger_jenkins_build_continue':
    require => $trigger_jenkins_require,
  }

all my testing gets me is errors:

Could not find resource 'Class['mm::common']' in parameter 'require'

it seems like the hiera ends up passing the array as strings