Skip to content
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.

No response for kv-read on valid path with a valid ACL token, but not relevant to the path being read #36

Open
ramukima opened this issue Jul 22, 2016 · 0 comments
Assignees

Comments

@ramukima
Copy link

By default, acl denied at Consul startup.

I have a path a/b/c protected by acl-1. Another path d/e/f protected by acl-2. I attempted the following that silently comes out without any response.

consul-cli kv read a/b/c --token acl-2-token

acl-2-token is a valid token but not for path a/b/c. The response was nil. It will be easier to write error on the CLI output if the HTTP call even in this case if any.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants