[FEATURE] Improve default error logging about go-sdk HOT 4 CLOSED

@rcrowe would you be willing to improve the log message? I think that would be a good place to start.

from go-sdk.

Thanks for bringing this to attention.

I wonder whether we ought to amend the ProviderResolutionDetail.Error() func to append the message to the error code, I agree that in its current state there isn't enough information provided by the default logger to be all that useful.

As for whether the default logger logs or not I'm still leaning towards errors being logged by default as it can be frustrating for something to not be working and seeing no indication of that in the logs. I'd like to hear other opinions on the matter @james-milligan @toddbaert @beeme1mr

from go-sdk.

It sounds like there are two issues here. First, the error log is missing key information in order to be useful. It definitely makes sense to improve that error message (and quickly review other log messages). Second, is the the default logging behavior. I would expect there not to be any logging during normal behavior. Originally, I felt it was a good idea to log errors by default but perhaps that's best left up to the user to decide. This seems like something we can change based on user feedback. If the general consensus is to no-op by default, let's do that.

from go-sdk.

Thanks @rcrowe, you change will be included in the next release.

from go-sdk.