You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tell us about the bug
When using token in QuixStreamingClient with a token and Quix__Workspace__Id is specified as environment variable, the client freaks out if token isn't valid for the workspace id. This should be also an optional parameter to pass and not use the environment variable when the token is passed in. This is because these tokens are used mostly when the intent is to interact with a different workspace than the current the application is deployed into. This feature was introduced in https://github.com/quixio/quix-streams-dotnet/releases/tag/v0.6.2
What did you expect to see?
It not failing with exception saying token is for Y workspace but env is configured for X
What version of the library are you using?
0.6.3
Workaround?
var prev = Environment.GetEnvironmentVariable("Quix__Workspace__Id");
var newVal = Environment.GetEnvironmentVariable("source__workspace__id");
Environment.SetEnvironmentVariable("Quix__Workspace__Id", newVal);
// do thing with QuixStreamingClient
Environment.SetEnvironmentVariable("Quix__Workspace__Id", prev);
The text was updated successfully, but these errors were encountered:
Tell us about the bug
When using token in QuixStreamingClient with a token and
Quix__Workspace__Id
is specified as environment variable, the client freaks out if token isn't valid for the workspace id. This should be also an optional parameter to pass and not use the environment variable when the token is passed in. This is because these tokens are used mostly when the intent is to interact with a different workspace than the current the application is deployed into. This feature was introduced in https://github.com/quixio/quix-streams-dotnet/releases/tag/v0.6.2What did you expect to see?
It not failing with exception saying token is for Y workspace but env is configured for X
What version of the library are you using?
0.6.3
Workaround?
The text was updated successfully, but these errors were encountered: