Puppet Community

&gt;&gt;&gt; require: Applies a resource after the target resource.
notify: Applies a resource before the target resource. The target resource refreshes if the notifying resource changes.

From <https://puppet.com/docs/puppet/8/lang_relationships.html|https://puppet.com/docs/puppet/8/lang_relationships.html>

You cannot apply the same package before AND after :)

I guess you want to notify the Service[httpd] instead 

you need to remove "notify", and not "require".

You can't require and notify same resource at the same time
Most likely you meant to notify service there, there is no point to notify a package

ah I guess it's fine after a puppet run which removes puppet-release.list because I have puppetlabs/puppetlabs-apt purging unmanaged

History is available here now: <https://www.linen.dev/s/puppetcommunity/c/puppet>

<@U11HA7VJ7> Please add this to the channel topic :pray::skin-tone-2:

set the channel topic: Welcome! <http://pup.pt/conduct|pup.pt/conduct> | Flag a message for moderation with the :moderator: reaction | Tell us about something awesome: <http://pup.pt/mvp|pup.pt/mvp> | Logs: <https://www.linen.dev/s/puppetcommunity/c/puppet>

Black Lives...

I guess you may try Debian packages then.. or you might consider to run it in a container (docker/podman/systemd-nspawn/lxc)

Good morning puppet people. I have a query on format of code.

What's the difference between these 2 lines of code?

```create_resources(Postgres::Instance, $instances, $instance_defaults)```
and
```create_resources(postgres::instance, $instances, $instance_defaults)```

I can't find this in the puppet docs as to why they act differently

The difference is capital P and I
<https://www.puppet.com/docs/puppet/8/lang_data_resource_reference.html>
The general form of a <https://www.puppet.com/docs/puppet/8/lang_resources.html#lang_resources|resource> reference is:
• The resource type, capitalized. If the resource type includes a namespace separator `::`, then each segment must be capitalized.


I guess the question raised because the create_resources function example in docs has “user” type lowercased

<https://www.puppet.com/docs/puppet/8/function.html#create-resources|https://www.puppet.com/docs/puppet/8/function.html#create-resources>

how to have a specific module run once every thirty days?

if i'm listing the module in the environments puppetfile.. it will get run every time the agent checks in correct?

specifically i'm generating a new ssh key every 30 days, rotating that with a puppet module.

This is a bit strange as puppet is about maintaining a specified state per agent.

You could do something like this by having conditional logic to include a class only if “time now” is for the first day of the month. Trying to do this on something like an “apply count” will be difficult.

Another alternative is to have a custom fact that depends on “time / count”. Then conditionally include the logic based on that fact.

yeah use a fact to report the key age and renew it if its too old

in fact I am pretty sure at least one of the ssh modules already reports it

I would also think about replacing ssh host key regeneration with an ssl ca that is centrally managed

so instead of needing to rotate those keys, you just ensure it's part of the ca

Maybe you mean something deeper, but this would be my starting point:
<https://www.puppet.com/docs/puppet/7/upgrade.html>
<https://www.puppet.com/docs/puppet/7/upgrading-from-puppet6-to-puppet7.html>

Thanks! I'll note these in our upgrade planning documents. I should also mention that we're using serverless puppet agent only, where  we're pulling the puppet code down to the local systems.

Anyone have ideas managing mounts with windows clients? Specifically Samba and NFS network mounts.

Unrelated, look like some copy/paste gone wild over here <https://github.com/puppetlabs/puppetlabs-mount_core/blob/main/lib/puppet/provider/mount/parsed.rb#L19-L21>. Easy bug to fix...

:businessparrot: _Content and Tooling_ is about to start up in <#CFD8Z9A4T|>

hello. If you're using OSP and want to share your experience and insights, I'd love to hear them. pls ping me  :slightly_smiling_face:

In what regards, Karla.  Most of us on this channel are OSP.  PE is mostly in <#C19V5U41Z|>