@bastelfreak @vchepkov in puppet 7.x, the

include_legacy_facts

controls whether the agent sends legacy facts to the server, but they are still available for type/provider confines/suitability. I see @smortex submitted a PR for fqdn_rand, which we'll need to update in 7.x. In Puppet 8, we're going to switch all of puppet's type/providers to using structured facts, so that we can finally cut the cord on legacy facts.

ahhhh ok

Good 13:34 EST. I'm trying to add "Managed by Puppet. Do not edit" to this define but I'm having trouble appending a single "managed by puppet line" with concat/concat::fragment. The tnsnames.pp define manages a single file so it could get called multiple times for multiple entries in the same file. I've looked at other modules' concat::fragment for a clue on how to make this happen but so far I've been unsuccessful. What would be a good way to have "managed by puppet" at the beginning of the file without having it repeated every time the define is instantiated?

Good 13:34 EST. I'm trying to add "Managed by Puppet. Do not edit" to this define but I'm having trouble appending a single "managed by puppet line" with concat/concat::fragment. The tnsnames.pp define manages a single file so it could get called multiple times for multiple entries in the same file. I've looked at other modules' concat::fragment for a clue on how to make this happen but so far I've been unsuccessful. What would be a good way to have "managed by puppet" at the beginning of the file without having it repeated every time the define is instantiated?

So far, all of examples I've looked at for concat::fragment create multiple, separate files instead of a single file with multiple entries.

You need to use a concat::fragment with a lower number

order

than the rest of the fragments.

Yes, but won't I have a duplicate definition?

And put that in a class that's shared by all declarations of that define type.

Unfortunately, there is no class that declares tnsnames.pp. I'll see about how to do that.

e.g. in the define, add

include oradb::tsnames::header

Then create that new class called

oradb::tsnames::header

that contains just a single concat::fragment

e.g. in the define, add

include oradb::tsnames::header

Then create that new class called

oradb::tsnames::header

that contains just a single concat::fragment

Not a class that declares tsnames.pp, but a class that is declared by tsnames.pp

Won't that create a duplicate resource definition?

No. Since Puppet only ever declares classes once regardless of how many times you

include <some_class>

No. Since Puppet only ever declares classes once regardless of how many times you

include <some_class>

Ahhh....I see that. Let me give that a try. Thank you.

letsplay 🧑‍🏫Puppet Core Team is about to start up in #CFD8Z9A4T

@natemccurdy something like this?

Yup, that looks correct.

This message was deleted.

I posted my code snippet in one of the threads

message has been deleted

This message was deleted.

So the reason it doesn't install a package in Puppet 4 with the zleslie module is because of this bit of code: 1) There's an

if

condition to check of the

$package_name

variable is set: https://github.com/voxpupuli/puppet-unbound/blob/1.3.2/manifests/init.pp#L79 2) And for freeBSD, it's set to

undef

, which means the package will not be installed: https://github.com/voxpupuli/puppet-unbound/blob/1.3.2/manifests/params.pp#L50

So to get similar behavior as the old module, and do what you want of not trying to install the package, you could either: A) Declare the

unbound

module with the

package_name

parameter set to an empty string. e.g.

class { 'unbound':
  package_name => '',
}

B) Or if you use Hiera, add an environment level piece of Hiera data for

unbound::package_name

that is the empty string:

''

So to get similar behavior as the old module, and do what you want of not trying to install the package, you could either: A) Declare the

unbound

module with the

package_name

parameter set to an empty string. e.g.

class { 'unbound':
  package_name => '',
}

B) Or if you use Hiera, add an environment level piece of Hiera data for

unbound::package_name

that is the empty string:

''

. e.g.

---
# Somewhere in an environment-level Hiera data file.
unbound::package_name: ''

This message was deleted.

My experience was absolutely broken in PE 2019.x. Lots of memory issues and constant restarts. Support should be able to confirm that it's not recommended

How to manage facts cache reported to puppetdb ?

facter -p

show correct value of custom facts but

puppet facts

show old one

puppetserver version: 7.9.3
puppet 7.21.0
puppetdb version: 7.12.0
facter 4.2.14

any advise how to manage that ?

This message was deleted.