On Wednesday, February 17, 2016 at 10:34:13 PM UTC+1, Trevor Vaughan wrote:
>
> Yeah, it would.
>
> What I'm looking at doing would be injected as part of the reporting phase
> so it would be updated after each client run.
>
> Not an ideal solution, I would much rather be able to add some extra
>
On Wednesday, February 17, 2016 at 10:34:13 PM UTC+1, Trevor Vaughan wrote:
>
> Yeah, it would.
>
> What I'm looking at doing would be injected as part of the reporting phase
> so it would be updated after each client run.
>
> Not an ideal solution, I would much rather be able to add some extra
>
On 02/17/2016 07:48 AM, Trevor Vaughan wrote:
I took a look at the API and it seems like I might have to use
'replace_facts' but I'd need to fetch the last fact set, update it,
and then resubmit it with the updated information which isn't ideal
but would be doable.
This is your best bet u
Yeah, it would.
What I'm looking at doing would be injected as part of the reporting phase
so it would be updated after each client run.
Not an ideal solution, I would much rather be able to add some extra
metadata to my clients in PuppetDB instead of needing to drag around yet
another database i
wouldnt next puppet run replace your out of band added fact?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view
Hi All,
Is is possible to add facts to a client in PuppetDB independently of a run
of Puppet on a client?
Basically, I need to add some data to the client runs but the data is
irrelevant to the client itself so there's no need to shove it across the
network multiple times.
I took a look at the A
