Closed Hansanto closed 1 year ago
Hi, @Hansanto! Thank you for your feedback and desire to improve Vault. At this time, Vault does not have API versioning that would enable the introduction of backward incompatible changes while preventing negatively impacting users that might depend on existing functionality. With that said, we will not be able to resolve this issue at this time. I have labeled it accordingly, however, so that we can reference it it later if/when proper API versioning is introduced to Vault.
Describe the bug The endpoint Read Secret ID will return an empty body with a status 2xx if the secret ID was not generated by the endpoint the Generate Secret ID and therefore, not found.
However, for other endpoints (for AppRole), when an element is not found (Read Role, Read Secret ID Accessor, List, etc.), the API will return a 4xx status code and not a 2xx with empty body.
To Reproduce
Expected behavior The Read secret ID should return 4xx if the value is not found (consistency with other endpoints)
Environment:
vault status
):Vault CLI Version (retrieve with
vault version
): Vault v1.15.1 (b94e275f25ccd9011146d14c00ea9e49fd5032dc), built 2023-10-20T19:16:11ZServer Operating System/Architecture: Docker on Windows & Linux
Vault server configuration file(s):
Additional context