Closed chris-gibbs closed 3 years ago
Glad that the project is of help to you. :)
I skimmed through the codebase and from what I found it should theoretically be protected by the handle_errors decorator, since resolve_by_name uses _request function from Connection.py.
I'll look into this
I found the problem. When doing a refresh, the initial request in not being retried. I have added the missing functionality and will publish the changes in v1.0.9
Firstly, great library! Really saves me a heap of time compared to access the FMC API directly.
I'm trying to run through ruleset sequentially to move lots of access rules into categories, however I think this could be triggered on also everything that relies on resolve_by_name.
Mostly working but hit a issue that I have not been expecting. I'm really not parsing responses for invalid token because from my understanding the wrapper @utils.handle_errors on Connection _request should be handling token refresh and retry.
That reasoning seems to be okay but I also happened to be using resolve_by_name and that doesnt seem to be protected by handle_errors.
Can the wrapper in resolve_by_name also be sent through handle_errors?
In the meantime, I will update my code to not be as lazy and only utilise the resolve_by_name on the first call to get the UUID for future calls.
I happened to be running it in a debugging session in FMC and also had pigtail running.
VSCode Stack Trace
Pigtail stack trace