Transit UX improvements: show key policy, configs on write #20652
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
Signed-off-by: Alexander Scheel <[email protected]>
This includes creating a key, but also trimming or rotating an existing key. Signed-off-by: Alexander Scheel <[email protected]>
Signed-off-by: Alexander Scheel <[email protected]>
Signed-off-by: Alexander Scheel <[email protected]>
Signed-off-by: Alexander Scheel <[email protected]>
stevendpclark
approved these changes
May 18, 2023
tsaarni
added a commit
to Nordix/vault
that referenced
this pull request
Mar 8, 2024
…ashicorp#20652)" This reverts commit d52d307.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When writing to an endpoint, currently transit responds with
nil, nil, meaning any invalid parameter warnings are hidden, and the user doesn't know the results of the operation.We should respond with the key policy on writes (or, on the other endpoint, the config), to show users the changes they made and show any invalid parameter warnings that might've been ignored.