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 Jul 27, 2023. It is now read-only.
I noticed that the KeyValueClient does not support passing a token(acl token) for a PUT to the KV store.The client does have GET methods that let you pass a token as a query option.
The client has putValue() methods with PutOptions but PutOptions currently only supports 'cas', 'acquire' and 'release'.
There is not support for consul PUT v1/kv/?token=.
Can PutOptions be updated to allow passing a token parameter as well?
The text was updated successfully, but these errors were encountered:
Hello,
I noticed that the KeyValueClient does not support passing a token(acl token) for a PUT to the KV store.The client does have GET methods that let you pass a token as a query option.
The client has putValue() methods with PutOptions but PutOptions currently only supports 'cas', 'acquire' and 'release'.
There is not support for consul PUT v1/kv/?token=.
Can PutOptions be updated to allow passing a token parameter as well?
The text was updated successfully, but these errors were encountered: