Reuse TowerClient http client #6520
Open
+135
−109
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR reuses the http client in TowerClient to avoid problems when refreshing tower access token.
The Tower access token is used for reporting workflow progress and for the fusion license. They use the hxclient to manage the token refresh. However, when the token is refreshed, a new refresh token is also issued, invalidating the old one. This token is stored at the token manager object. As the fusion license creates a different client and token manager. It doesn't contain the new tokena and uses the old refresh token that is not valid.
Applying changes as in #6207
TODO: