>
>
> If that's your only alternative, and -- as we've already covered -- you
> must not use triggers, then you are out of luck. Puppet does not emit any
> notifications when exported resource data change. On the other hand, it
> does emit notifications when resource changes are applied to a
>
> (like stuff needing guy/rest-api to update config).. I'd still make puppet
> write config files.. perhaps in json format - and then simply catch puppet
> return code in script running puppet on the "config server that pulls the
> exported resources".. and post those new json files (filestam
>
> I'm not sure what you think I suggested. I said the *agent* reports when
> it *applies* changes. This includes changes associated with exported
> (possibly by other nodes) resources.
>
The agent is not involved at all in exporting resources, nor even directly
> in collecting exported re
>
> As I said, that's a very odd way of doing things. It's odd on at least
> two levels:
>
> 1. it's a bit odd that you want to configure the application by
> dynamically submitting data to the service, instead of by directly managing
> its configuration data store. This approach has negative
>
> If you can get by with less data, and if your catalog runs normally go
>> complete without any changes, then you could perhaps also run the agent via
>> a scheduler (instead of as a daemon), with the --detailed-exit-codes option
>> turned on, and trigger your middleware based on the agent r
On Tuesday, March 15, 2016 at 3:50:28 PM UTC+1, jcbollinger wrote:
>
>
>
> On Monday, March 14, 2016 at 11:23:53 AM UTC-5, Jelle Smet wrote:
>>
>> Hi list,
>>
>>
>> I have a Puppet module (internal to the company) which makes use of
>> exported re
Hi list,
I have a Puppet module (internal to the company) which makes use of
exported resources.
The exported resource data stored in PuppetDB is used to configure an
external application.
I'm looking for a way to notify this external service in order to trigger
it load the stored exported re
