feat: add object format to support pfx #175
Merged
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.
What this PR does / why we need it:
objectFormat
field that user can configure topem
orpfx
. Default format ispem
.pfx
will return the raw data (base64 encoded) as is from the Key VaultobjectFormat: pfx
is only supported withobjectType: secret
as key vault only supports pfx format for type secret.key
andcert
objects are returned inpem
format.Which issue(s) this PR fixes (optional, using
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when the PR gets merged):Fixes #138
Special notes for your reviewer:
az keyvault secret download
This change adds a similar behavior, providing user the option to set
objectFormat: pfx
for secret type.