vault4s
vault4s copied to clipboard
Fix transit uris
Don't uri encode the key in the transit endpoints.
This is consistent with how dynamic uris are created within Vaults
(example).
Should probably leave a warning as this will now break if {key.name}
starts with /
, I mean no worse than we are presently broken. But good that we make that clear in documentation somewhere.
Looks like this got bogged down as a change in behavior. Can we get it into the 8.x and 9.x releases?