Closed brunoguic closed 10 months ago
I'm unsure if the error should be reported to the SDK team. Upon inspecting the SDK code, the following observations can be made:
PollingProjectConfigManager.SyncConfig
function, the error is handled correctly, and it populates the err
variable with the 403 error code.PollingProjectConfigManager.GetConfig
, the err
variable is not exposed. This omission occurs because, after a series of successful requests, the projectConfig
is no longer nil
.Hi @brunoguic Thanks for creating the issue here. Currently the same team maintains the Agent and SDK. We'll look into this and get back to you.
Hi @brunoguic We have decided to improve the error handling to convert the previous warning logs to error logs. For running Agent in Kubernetes, we are also recommending to setup monitoring & alerting system to capture such error logs ASAP.
Is there an existing issue for this?
Agent Version
2.7.0
Current Behavior
After an instance of
PollingProjectConfigManager
suffers a 403 error, the Agent will not be able to identify, nor recover from this bad state.Expected Behavior
The Agent could identify and try a new authentication, or kill itself.
Steps To Reproduce
Go Version
1.18
Link
No response
Logs
No response
Severity
Affecting users
Workaround/Solution
After we identify the error, we can restart the Agent to force a new authentication.
Recent Change
No response
Conflicts
No response