Accessing UI with unauthenticated and/or expired token lead to a crash
Accessing Nomad via nacp with resolve token enabled will lead to a crash since we pass and empty pointer to applogger, so now we will only try to log if a token is render regardless if enabled or not.
The second part is to change to only log when a token resolution fail, so avoid use popups like the attached image shows
@mxab I will leave as a draft until I find all the corner cases :)
We've been running with this patch since last week and found no more issues. So I'm happy with it now.
Hi @ncode really sorry for picking this up now, I was in the middle of the otel stuff and just had the time to review and reproduce it now.
I'm currently trying to setup a test for it now an wondering if we should either "ignore" the resolving error like you do it or actually check if is one of the actionable calls i.e. registry, plan or validate and only do then the resolving?
I hope you don't might that I'm closing this PR as I think the way where we handle only relevant requests is more suitable #49