This message was deleted.
# puppets
Slackbot
06/01/2023, 2:49 PMThis message was deleted.
b
bastelfreak
06/01/2023, 2:50 PMthe resources it exports or the ones that are realized on the agent?
y
Yehuda Katz
06/01/2023, 2:51 PMIt exports
b
bastelfreak
06/01/2023, 2:51 PMmhm I don't think so because the agent isn't aware of the old version of the resource
y
Yehuda Katz
06/01/2023, 2:51 PMMakes sense
Yehuda Katz
06/01/2023, 2:52 PMWould be a nice feature... For example, we have backend servers that export
@@haproxy::balancermemberb
bastelfreak
06/01/2023, 2:53 PMreverse the logic, check on your haproxy
bastelfreak
06/01/2023, 2:53 PMfor example do a puppet run with --noop to check for changes first
y
Yehuda Katz
06/01/2023, 2:53 PMThat is what I am doing, but I was wondering if there was a way to make it faster by checking the export itself
Yehuda Katz
06/01/2023, 2:54 PMIt would probably require a lot of changes - give PuppetDB a way to send back to the agent what changes it got, and a way for the agent to show that.
b
bastelfreak
06/01/2023, 2:54 PMyes and you don't gain much. just because the agent exports something doesn't mean another agent will import it
s
saz
06/01/2023, 4:18 PMIt might also change during realization on the haproxy, which isn't known to the exporting agent at all.
y
Yehuda Katz
06/01/2023, 4:19 PMRight - all it would be able to do is say that the values of the exported resource itself have been changed, but it doesn't know what is going to happen as a result.
Yehuda Katz
06/01/2023, 4:20 PMI still think that could be useful
s
saz
06/01/2023, 4:30 PMIn some cases, it might be. As long as you're always remembering, that it's not the final result 🙂