runs twice a week

yeah that hiera option basically includes the pe_databases class I linked above

Puppet fact data can be "bursty". Autovaccum can't help with a set of facts that report large values on one run and then stop. Space has to be allocated to hold the large dataset, even if ends up being transient. All autovaccuum can do is ensure space is re-used once allocated.

Long-running transactions are also another item that can cause growth. Autovacuum can only clean up rows that died before the oldest transaction started. If you've got a query that runs for hours or days, then several puppet runs worth of writes will need to allocate new disk space rather than moving into the space vacated by previous data.

So, the three scenarios where table size starts to grow are: • The size of the live data set increases, perhaps due to facts, catalogs, or reports temporarily being larger than normal. • The age of the oldest in-progress query starts increasing. • The time required to autovacuum the table becomes larger, so more churn builds up between runs. Usually, one of the first two scenarios occurs. Time required for autovacuum to process the table increases with table size, so the third scenario item usually shows up as a "death spiral" resulting from one of the first two pushing the system past a tipping point.

businessparrot 🧑‍🏫PE Console is about to start up in #CFD8Z9A4T

This message was deleted.

This message was deleted.

This message was deleted.

The issue here I think from your code above is the title you have given is "install test" it will therefore be looking for "install test" to be installed. Either you can change the title or add a name attribute which is the name as it appears to RPM

The issue here I think from your code above is the title you have given is "install test" it will therefore be looking for "install test" to be installed. Either you can change the title or add a name attribute which is the name as it appears to RPM ( presumably test? )

This message was deleted.

hi all, I have variables in

init.pp

and I want access those variables in

mytestclass.pp

, I tried like this :

$package_name

it doesnt work. or

notify {"${package_name} is package name": }

it doesnt work either. but the vairables in

init.pp

are in a

case of osfamily

. maybe thats why the

mytestclass.pp

cannot access it ? thank you all

hi all, I have variables in

init.pp

and I want access those variables in

mytestclass.pp

, I tried like this :

$package_name

it doesnt work. or

notify {"${package_name} is package name": }

it doesnt work either. or $::package_name but the vairables in

init.pp

are in a

case of osfamily

. maybe thats why the

mytestclass.pp

cannot access it ? thank you all

hi all, I have variables in

init.pp

and I want access those variables in

mytestclass.pp

, I tried like this :

$package_name

it doesnt work. or

notify {"${package_name} is package name": }

it doesnt work either. or

$::package_name

but the vairables in

init.pp

are in a

case of osfamily

. maybe thats why the

mytestclass.pp

cannot access it ? thank you all

thanks again @David Sandilands I was now on the page and I solved,

$classname::package_name

in

mytestclass.pp

Question: ask further are init.pp and mytestclass.pp both in a module? Answer: yes both are in a module

This message was deleted.

hi, i am a little bit stuck with the puppet build-in

match

function. I try to parse a loaded file (

file()

) via the match function and capture every block that matches my regex. The regex itself works but my problem is that

match

stops after the first match. Is there a flag that i did not found yet or a alternative function that allows a global matching of my regex?

This message was deleted.

I'm looking at the puppet apache module and they seem to do a mixture of both.

Which confuses me further.

Optional default value is undef, in your case is just a string or Stdlib::Unixpath

Optional default value is undef, in your case is just a string or Stdlib::Unixpath

I prefer in class, but it's a matter of preference

This message was deleted.

I'm pretty sure I'm abusing Heira.

if you only have common.yaml then it makes sense to remove it and hiera.yaml completely and save yourself some lookups

in a module

This message was deleted.

Found the ruby

scan()

function and wrote now my own puppet function in ruby:

# Matches a pattern against a string and returns an array containing
# every match.
# If the pattern contains no groups, each individual result consists of the
# matched string. If the pattern contains groups, each individual result is
# itself an array containing one entry per group.
#
# @see <https://apidock.com/ruby/String/scan>
#
Puppet::Functions.create_function(:scan) do
  dispatch :scan do
    param 'String', :string
    param 'Variant[String,Regexp]', :Pattern
    return_type 'Array'
  end

  def scan(string, pattern)
    string.scan(pattern)
  end
end