Re: [Puppet Users] Avoiding duplicate exported resource

I've managed to solve this with query_resources() from puppedbquery to generate an array of the resources and ensure_resource() to only create a single instance. That seems to be the cleanest way at the moment to handle this. On Mon, Mar 7, 2016 at 9:25 AM, Ken Barber wrote:

Re: [Puppet Users] Avoiding duplicate exported resource

>> Model wise, in an ideal world, the proxied/virtual address would be a >> 'node' of sorts, and have that entry, but if no box exists to compile >> that catalog, well then we're just talking crazy :-). >> > > > Well no, if the proxied / virtual address is not a property specific to any >

Re: [Puppet Users] Avoiding duplicate exported resource

On Thursday, March 3, 2016 at 11:51:13 AM UTC-6, Ken Barber wrote: > Model wise, in an ideal world, the proxied/virtual address would be a > 'node' of sorts, and have that entry, but if no box exists to compile > that catalog, well then we're just talking crazy :-). > > Well no, if the

Re: [Puppet Users] Avoiding duplicate exported resource

Exported resources won't handle any resource de-duplication. You can get around this by simply not using that to collect data, dalen's puppetdb-query will help with this, and in PDB 4.0 we're introducing a function for this purpose also into core. Once you have the data, then you can do anything

[Puppet Users] Avoiding duplicate exported resource

I've created a module to configure a caching nginx proxy. I am running several of these proxies behind a load balancer. They all proxy the same external address. I'd like to export a nagios host/service for monitoring the external address, which will then be collected on my nagios server. The