On Monday, April 16, 2018 at 10:38:55 AM UTC-5, Trevor Vaughan wrote:
>
> How difficult would it be to create a third type of resource which is an
> 'ephemeral resource' whose only purpose is data collection on a host to be
> used by some other collector?
>
> These items would not be part of
How difficult would it be to create a third type of resource which is an
'ephemeral resource' whose only purpose is data collection on a host to be
used by some other collector?
These items would not be part of the catalog or added to the graph but
would instead just hang around for reference
In terms of #2, there's actually a ticket that I put in a while ago for a
shared data cache.
But, I recently realized that the common pattern is to literally map every
line in a file as a separate resource. We've had the same issue with
firewall rules, etc... for quite some time. So, the most
On 16/04/18 17:38, Trevor Vaughan wrote:
How difficult would it be to create a third type of resource which is an
'ephemeral resource' whose only purpose is data collection on a host to
be used by some other collector?
These items would not be part of the catalog or added to the graph but
I thought there were dangers with Virtual Resource being accidentally
realized sometimes?
We found a super-hacky way to call functions at the end of a compile which
we use in
https://github.com/simp/pupmod-simp-compliance_markup/blob/master/manifests/map.pp.
It would be *really nice* if there
