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
{{ message }}
This repository has been archived by the owner on Mar 11, 2020. It is now read-only.
As far as I understand, consul token is currently a property of interpreter. Which means, that we need interpreter per token.
Would you consider adding support for setting token on operation level rather than globally on interpreter level?
If yes, how would you suggest implementing the change (should we maintain backward compatibility, should we simple add token property to all operations, etc.)?
If not, how would you suggest workaround the issue? I mean, how would you suggest organizing the code?
The text was updated successfully, but these errors were encountered:
koiuo
changed the title
design: support for per-request token
question: support for per-request token?
Nov 29, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As far as I understand, consul token is currently a property of interpreter. Which means, that we need interpreter per token.
Would you consider adding support for setting token on operation level rather than globally on interpreter level?
If yes, how would you suggest implementing the change (should we maintain backward compatibility, should we simple add token property to all operations, etc.)?
If not, how would you suggest workaround the issue? I mean, how would you suggest organizing the code?
The text was updated successfully, but these errors were encountered: