Auth token in extra_headers expires on long running tests

[JimPaine]

I am using Azure Log Analytics to push test results to. Example here

Like many storage services it uses a client crendential flow to obtain a short lived bearer token.

Currently the logging handler is initialized at the start of the test session, but then not called until the end of the test session. When running longer tests this causes the token to not be valued by the time it is used.

[vkarak]

You are right. Currently, you can't modify dynamically the headers. Did you manage to work around it, though? As I don't see an immediate workaround from the user's perspective.

Maybe reframe could call back to the user in case of a request error. In this case you could update the token and reframe would retry.

[JimPaine]

My scenario is a little more automated where the token is obtained by a node level identity rather than a user.

My current thoughts are to add a callable to the httpjson handler which we can call in the emit method right before we make the request.

I have an intital attempt here and would love feedback and thoughts.

I have run a short test and it works and I am currently running a ~24hr test now to ensure the token would have expired if it was set during the init stage of the handler.

Edit: If you are happy I could always raise it as a draft PR, may be easier to collaborate on.