Am Montag, dem 31.10.2022 um 20:57 -0700 schrieb Robin Lee Powell:
I don't think we're going to be able to help further without a
fully-working minimal example.
Found the reason. I include classes by Hiera lookup. It works if I put the
defaults BEFORE
lookup('classes', { merge => unique }).inc
I don't think we're going to be able to help further without a
fully-working minimal example.
On Mon, Oct 31, 2022 at 02:32:21PM +, 'Dirk Heinrichs' via Puppet Users
wrote:
> Am Montag, dem 31.10.2022 um 15:29 +0100 schrieb Martin Alfke:
>
> How do you declare some_resource type?
> Are you u
Am Montag, dem 31.10.2022 um 15:29 +0100 schrieb Martin Alfke:
How do you declare some_resource type?
Are you using standard type declaration:
some_reosurce { ’title’:
param => ‘value,
…
}
Yes, like this.
Or do you use ensure_resource or create_resource function?
No, I don't use any of the
Next guess:
How do you declare some_resource type?
Are you using standard type declaration:
some_reosurce { ’title’:
param => ‘value,
…
}
Or do you use ensure_resource or create_resource function?
> On 31. Oct 2022, at 15:19, 'Dirk Heinrichs' via Puppet Users
> wrote:
>
> Am Montag, dem
Am Montag, dem 31.10.2022 um 15:10 +0100 schrieb Martin Alfke:
Is attribute the correct parameter of some_resource type?
Yes.
You mention that notify returns the desired results, therefore I assume that
hiera returns a proper value for ’some.key’.
Which means that the if facts clause is also wo
Hi Dirk,
Is attribute the correct parameter of some_resource type?
You mention that notify returns the desired results, therefore I assume that
hiera returns a proper value for ’some.key’.
Which means that the if facts clause is also working as expected.
Are you overwriting the Some_resource def
Hi,
I'm currently stuck with a problem where resource defaults from site.pp are not
applied, for example:
if $facts['custom'] == 'some value' {
Some_resource { attribute => lookup('some.key'), }
notify { lookup('some.key'): }
notify { $facts['custom']: }
}
The two notifications appea
