This repository was archived by the owner on Mar 15, 2024. It is now read-only.
Return a client error when a nodeID is not found #34
Conversation
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
At present, if a client passes in an invalid ID to the /creds/<role>/<NodeID> endpoint, vault returns a 500 This change updates the error to be a 400 level return code Other changes include updates for golang and deps
harsimranmaan
force-pushed
the
error_message_update
branch
from
4aa7200 to
3abd871
Compare
harsimranmaan
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
At present, if a client passes in an invalid ID to the /creds/[role]/[NodeID] endpoint, vault returns a 500
This change updates the error to be a 400 level return code
Other changes include updates for golang and deps