6f66e5cd48
* Allow reading Nomad CA/Client cert configuration In the Nomad secret engine, writing to /nomad/config/access allows users to specify a CA certificate and client credential pair. However, these values are not in the read of the endpoint, making it hard for operators to see if these values were specified and if they need to be rotated. Add `ca_cert` and `client_cert` parameters to the response, eliding the `client_key` parameter as it is more sensitive (and should most likely be replaced at the same time as `client_cert`). Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com> * Add changelog Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com> * Fix tests to expect additional fields Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com> * Add test with existing CA/client cert+key Signed-off-by: Alexander Scheel <alex.scheel@hashicorp.com> |
||
|---|---|---|
| .. | ||
| cmd/nomad | ||
| backend.go | ||
| backend_test.go | ||
| path_config_access.go | ||
| path_config_lease.go | ||
| path_creds_create.go | ||
| path_roles.go | ||
| secret_token.go | ||