Fix the update endpoint for the role configuration to behave according to POST RESTful definitions. Add a PATCH endpoint for the role configuration.
This change might affect users that misuse the POST endpoints to update individual fields in the role configuration. If they omit required fields, this will now return an error, and if they simply omit fields, these will not be changed back to defaults (as opposed to keeping the value that was previously configured).
Design of Change
I reused most of the code that used to be the update function for the patch method (as it actually behaved like a patch). Also refactored some code into own methods to reduce code duplication.
Overview
Fix the update endpoint for the role configuration to behave according to POST RESTful definitions. Add a PATCH endpoint for the role configuration.
This change might affect users that misuse the POST endpoints to update individual fields in the role configuration. If they omit required fields, this will now return an error, and if they simply omit fields, these will not be changed back to defaults (as opposed to keeping the value that was previously configured).
Design of Change
I reused most of the code that used to be the update function for the patch method (as it actually behaved like a patch). Also refactored some code into own methods to reduce code duplication.
Related Issues/Pull Requests
[ ] Issue #163 [ ] Vault PR #17371
Contributor Checklist
[x] Add relevant docs to upstream Vault repository, or sufficient reasoning why docs won’t be added yet Vault PR #17461 [ ] Backwards compatible