client-go
client-go copied to clipboard
Allow operating on errors instead of logging them
At the moment, there is no option to avoid logging certain errors, which also prevents dependent repositories from operating on these errors in a way that would make more sense to the user-facing side of things. IIUC, it makes sense to use HandleError
for all non-user-facing facets, but not so much in cases where this ends up adding to the confusion of the user since the caller had no way to deal with these errors.
A bit of context; at the moment, I'm using reflectors to update stores which are dynamic in nature, in the sense that these can be operated on to add or drop certain resources. This however, leads to reflector.go
logging whenever a previously-found resource goes "missing". Is there a possible workaround to this, or maybe something that I'm completely failing to see?