Create a list-all api endpoint for listing/finding the secrets available#32012
Open
pschou wants to merge 2 commits into
Open
Create a list-all api endpoint for listing/finding the secrets available#32012pschou wants to merge 2 commits into
pschou wants to merge 2 commits into
Conversation
dosubot
Bot
added
the
size:L
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
|
@pschou is attempting to deploy a commit to the HashiCorp Team on Vercel. A member of the Team first needs to authorize it. |
Add a new /sys/secrets/list-recursive endpoint that lists all secrets across all secret engine mounts with optional filtering by path, glob pattern, fuzzy substring matching, and ACL permissions. The response includes key_info metadata for each secret (mount path, type, accessor). CLI integration: - Extend vault list command with --all-mounts, --recursive, --fuzzy, --pattern, --permissions, and --recursive-mode flags - New ListRecursiveInput struct in the Vault API SDK for programmatic access API client changes: - Add ListRecursive() and ListRecursiveWithContext() methods to the Logical backend client Tests: - Unit tests for shouldFilterKey (glob + fuzzy matching logic) - Integration tests covering all filter combinations via core.HandleRequest - HTTP-level integration tests exercising the full request/response cycle - Added key_info metadata validation in response
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
What does this PR do?
Problem: When a tech is at the command line and needs to look up the password for a particular device, but forgets which path the device credentials are stored in, the lookup can take a while. In the effort to make the list searchable (think: pipe grep) or list all the options for a name segment (think: list all the ILOMs), the ability to open this up via an API for a client call can help realize this as a solution.