cb1a686e3b
* Strip empty strings from database revocation stmts
It's technically valid to give empty strings as statements to run on
most databases. However, in the case of revocation statements, it's not
only generally inadvisable but can lead to lack of revocations when you
expect them. This strips empty strings from the array of revocation
statements.
It also makes two other changes:
* Return statements on read as empty but valid arrays rather than nulls,
so that typing information is inferred (this is more in line with the
rest of Vault these days)
* Changes field data for TypeStringSlice and TypeCommaStringSlice such
that a client-supplied value of `""` doesn't turn into `[]string{""}`
but rather `[]string{}`.
The latter and the explicit revocation statement changes are related,
and defense in depth.
|
||
|---|---|---|
| .. | ||
| testdata | ||
| backend.go | ||
| backend_test.go | ||
| field_data.go | ||
| field_data_test.go | ||
| field_type.go | ||
| lease.go | ||
| lease_test.go | ||
| openapi.go | ||
| openapi_test.go | ||
| path.go | ||
| path_map.go | ||
| path_map_test.go | ||
| path_struct.go | ||
| path_struct_test.go | ||
| path_test.go | ||
| policy_map.go | ||
| policy_map_test.go | ||
| secret.go | ||
| secret_test.go | ||
| template.go | ||
| testing.go | ||
| wal.go | ||
| wal_test.go | ||