ghz icon indicating copy to clipboard operation
ghz copied to clipboard

token expiration issue for longevity test (longer than 1 hour) on ghz

Open zbhuang2008 opened this issue 2 years ago • 0 comments

Command line arguments / config ghz -m '{"authorization":"Bearer my-token"}' ...

Describe the bug I'm passing an authorization header using metadata (one of the parameters of ghz). But the token is only valid for 1 hour. Because I am doing the longevity test using ghz, which will be 24 hours. I wonder in such case, what I can do to get this longevity test done. Right now I have an independent go program which can take service account json file and serviceUrl to create a valid token. One solution can be - In a loop, create a token, then pass the token to ghz, run it. then continue the loop. Basically put a wrapper outside of ghz. I wonder is there a better way to do this (say in ghz project itself) ? I am open for any suggestions/discussions. Thanks.

Relevant issues #120 Add support for authorization headers #367 Metadata not being passed to reflection endpoint

Environment

  • OS: macOS
  • ghz: 0.109.0 installed from brew

zbhuang2008 avatar Aug 11 '22 23:08 zbhuang2008