Skip to content
This repository was archived by the owner on Jul 27, 2023. It is now read-only.
This repository was 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

@ramukima

Description

@ramukima

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.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions