This repository has been archived by the owner on Jul 26, 2022. It is now read-only.
feat: add general support for isBinary for all backends #585
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
isBinary
inKVBackend
+ testsisBinary
from Azure Key Vault & GCP Secrets Manager backendsisBinary
field in the CRD to remove Azure-specific detailsBackground
isBinary
for specific backends, both using the same approachproperty
is not available inVaultBackend
, you cannot handle binary secrets there either.isBinary
inKVBackend
.isBinary
withproperty
- it is possible (and in fact a requirement for Hashicorp Vault).