-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UI: allow navigation to subdirectory #22455
Merged
hellobontempo
merged 12 commits into
ui/VAULT-16258/kv-ember-engine
from
ui/VAULT-19168/allow-navigation-to-subdirectory-2
Aug 21, 2023
Merged
UI: allow navigation to subdirectory #22455
hellobontempo
merged 12 commits into
ui/VAULT-16258/kv-ember-engine
from
ui/VAULT-19168/allow-navigation-to-subdirectory-2
Aug 21, 2023
Conversation
This file contains 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
Build Results: |
…ow-navigation-to-subdirectory-2
Approvals were on different branch/PR #22436 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
This partially fixes the request here #5362 so users can
LIST
at the secret level in the UI.Fixes #20563 and #13188 and #20563
The user in the gif has the following policy where they can only
LIST
at themy-secret/
level. Previously a user had to know the full secret path to view this list of secrets, now they just need the top-level secret path:If a user can only list metadata at the top level, so with a policy that looks something like:
The input in the card pre-fills with the path selected from the list view
