kv2/metadata: ReadSecretPathsAsync
allows empty path value to list all secrets on the mountPoint
#337
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the implementation of
the path is required which was built referencing -> https://developer.hashicorp.com/vault/api-docs/secret/kv/kv-v2#list-secrets
However, as reported in gh-334, it seems like
path
can be empty, if you want to list all the secrets on the mount point.I tried this with Vault v1.15.2, below are the results of my test.
Sample Request
Response
considering the above results, I felt removing the strict null check and adding a simple guard rail would be a better solution.
fixes #334