The JCasC offers the base64 and decodeBase64 helpers that can be applied to a secret prior to use, but they are not applicable here. Also, the secretBytes of a file Credential are automatically base64-decoded before being passed to a pipeline.
When migrating to hashicorp-vault-plugin (say from file Credential to vaultFileCredentialImpl), there is no way to retrieve the same behavior. A base64-encoded file that lies in Vault cannot be passed to a pipeline decoded already which forces us to modify the way pipelines handle such Credentials.
What feature do you want to see added?
The JCasC offers the
base64anddecodeBase64helpers that can be applied to a secret prior to use, but they are not applicable here. Also, thesecretBytesof afileCredential are automatically base64-decoded before being passed to a pipeline.When migrating to hashicorp-vault-plugin (say from
fileCredential tovaultFileCredentialImpl), there is no way to retrieve the same behavior. A base64-encoded file that lies in Vault cannot be passed to a pipeline decoded already which forces us to modify the way pipelines handle such Credentials.Did I miss anything ?
Thanks a lot
Upstream changes
No response