Puppet Community

Hello, everyone.  I’m trying to figure out what is the retention policy for puppet exported resource in puppetdb.  I just asked chatgpt and was told to set command-reprocessing-period in puppetdb.conf, but i can’t find any documentation about it.  Is there a default time limit?  Thank you.

I think if you search the puppetdb.conf documentation for "ttl" you'll find the configuration elements you want.

Or at all, given how much garbage and outdated data it was given for its learning sets.

an exported resource is removed from puppetdb when a node is deleted (maybe also when it is deactivated) or when a node delivers a new catalog without the exported resource

<https://fosstodon.org/@puppet/110198605815370791>

In the actual code, `$cert` and `$intermediate` are retrieved from Vault with a Deferred function that returns a Sensitive value:
```$cert         = Deferred('vault_lookup::lookup', ['secrets/cert'])
$intermediate = Deferred('vault_lookup::lookup', ['secrets/intermediate'])```

I also found that I can fix the problem by *not* using `inline_epp()`.

If I change the `$chain` variable to be this, it works:
```# This isn't ideal because the file needs a trailing newline, which join() can't do.
$chain = Sensitive(Deferred('join', [[$cert.unwrap, $intermediate.unwrap], "\n"]))```

I opened <https://tickets.puppetlabs.com/browse/PUP-11846>

I’d recommend you to use puppet-vaultbot module and forget about it ;)

The only problem you’ll have is how to get certificates before starting something.. which can be solved by systemd dependencies or by exec-ing the vaultbot service before dependent service 

Update: This fixes the problem:
```content =&gt; Sensitive(Deferred('unwrap', [$chain])),```

It's almost like the internal `unwrap` of the sensitive content isn't being deferred.

So explicitly deferring the unwrap gets around that... maybe?
I admit, I'm not entirely sure what the bug is nor how this solves it.

Here's a simpler reproduction:
```file { '/tmp/test.txt':
  ensure  =&gt; 'file',
  content =&gt; Deferred('new', [Sensitive, "hello world\n"]),
}```

<@U047TJ03KT7> That change you highlighted was a change to an internal, private part of the `mysql::password()` function.

You don't need to change how you call the function.

The `dispatch` portion of a Puppet function is its signature. That defines _how_ you're expected to use it, and that hasn't changed:
• <https://github.com/puppetlabs/puppetlabs-mysql/pull/1557/files#diff-f63c8340e97cb15646da94767358abc703a41ba144fa217d9585e00b8a04b289L16-L20>

Hmm... though, now that I read it, it does allow 1 or 2 parameters :confused:

:thinking_face:ok then i need debug more. Thanks so far

For me the change from `sensitive = false` to `sensitive: false` just was strange for me.

Have now open a GitHub issue for that one. Since i also found out that the rspec to test this case is set to be skipped...
<https://github.com/puppetlabs/puppetlabs-mysql/issues/1563>

Don't forget the hackathon tomorrow! <https://dev.to/puppet/may-the-source-be-with-you-45bi>

:party-dag:  :loudspeaker:  The hackathon will start in ~ 10 min for the folks in EMEA (CEST) :point_up:  :party-dag: :party-dag:

<https://docs.google.com/forms/d/e/1FAIpQLSc0jDa0SIFJjmBh9q2SoH55hIixFXbCWyedvGib5eUiRXyZbg/viewform?usp=send_form>

not again, this was also happening on <http://apt.puppet.com|apt.puppet.com> :disappointed:

we could also ask: <@U01MXBB09RC> <@UDDJQQZ38> <@U11HA7VJ7>

I just asked internally, we will check that, thanks for reporting it <@U047TJ03KT7>++ <@U11MKJ5D4>++

mail396 is on the rise! (Karma: 1)
rwaffen leveled up! (Karma: 2)

also <@U048W3UL9EU>++ for the inital hint of the issue:sweat_smile:

2022-10-26.slack.pupp is on the rise! (Karma: 1)

Hi everyone, I got a confirmation from our release engineering team that this should be fixed now!

Thanks for reporting it! :+1:

By coincidence I raised <https://tickets.puppetlabs.com/browse/DOC-5374> yesterday to add this to docs

I don't see that, it needs a login :disappointed:

it doesnt have the information in it of what the translation is

but just to highlight it has been asked for docs to provide this

not if you only want the disk names, as I said if you know how to get the disk only and not the map of all the details

`$blockdevices = $facts.get('disks', {}).map |$x| { $x[0] }`

something like that :slightly_smiling_face:

ah.. actually just `$facts.get('disks'. {}).keys()`

thanks <@UNNE9882X> I'm just attempting that now.

Is there a more verbose explanation to writing up classification rules in the puppet console? <https://www.puppet.com/docs/pe/2021.7/grouping_and_classifying_nodes.html#dynamically_add_nodes> really only discusses using facts, and not say how the regular expression system can/should/does match things etc?

e.g. do anchor patterns work at all with fact matching the certname/hostname?

I need a single character from the hostname to define it's environment

Oh, you want to extract that value from regex match? That's not going to work

e.g.
```if $certname =~ "/^..(D).*$/":
environment = development
elseif $certname =~ "/^..(T).*$":
  environment = testing```

you better off creating a fact based on that

people have been doing hostname matching classification for as long as puppet been around, why would I create a fact for my environment if the hostname clearly says the environment already?

since you are matching a string, not a line

ok, I swapped the ordering of the classes as it installed puppetdb and it was frozen on starting up because waiting on the db that wasn't installed yet

is there an override for the postgres package it installs? it has created a .repo file, but we don't allow outgoing connections

I started a prjoct like that for Aflac, but the infra was friggin' enormous

they did all kind of load balancing and app tricks on the frontend for agent connection

:indeed: _:teacher:PE Console_ is about to start up in <#CFD8Z9A4T|>

And to clarify, I'm using `epp()` to build a String, and just one of the parameters to `epp()` is sensitive.

For example:
```concat::fragment { 'foo':
  target  =&gt; $foo,
  order   =&gt; '01',
  content =&gt; epp('module/template.epp', 
    {
      'password' =&gt; Sensitive($password),
      'other'.   =&gt; $other,
    },
}```

I saw that at a customer a few times and I wasn't sure where it's coming from

they have some hiera logic to cast many values to Sensitive, I assumed that's the problem. Did you verify this is caused by the concat upgrade?

maybe the whole content needs to be sensitive now :thinking_face:

Yup, it works if the entire `content` value is wrapped in Sensitive.
But that kind of defeats the nice feature of epp() where only sensitive variables are redacted.

See the `puppetlabs-concat` module at <https://forge.puppet.com/puppetlabs/concat?src=slack&amp;channel=puppet>

Howdy.
How can we get <https://github.com/puppetlabs/puppetlabs-puppetdb/pull/351> merged?

Anyone know why the puppetlabs-lvm module has not been released to the forge for a while? The current version states puppet 7 not supported.
there's already an issue open for this <https://github.com/puppetlabs/puppetlabs-lvm/issues/276>

See the `puppetlabs-lvm` module at <https://forge.puppet.com/puppetlabs/lvm?src=slack&amp;channel=puppet>

someone said it is not a supported module :disappointed:

the last update to the main branch was in August, the tag is from 2020. It may not be supported by puppet directly, but it still seems to be supported by the community

```This module is supported by the Puppet community. We expect it to be of the same high quality as our own Supported modules, but it does not qualify for Puppet Support plans. See the CODEOWNERS file for usernames of the maintainers.

[tier:trusted-contributor]```