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.
Missed this update ready for release from #79
0.1.0 (March 24th, 2021)
CHANGES
objects
entryarray
entry underobjects
objectVersion
is now ignoredobjectPath
is renamed tosecretPath
secretKey
,secretArgs
andmethod
are newly available optionsobjectName
no longer determines which key is read from the secret's datasecretKey
is set, that is the key from the secret's data that will be writtensecretKey
is not set, the whole JSON response from Vault will be writtenvaultSkipTLSVerify
is no longer required to be set to"true"
if thevaultAddress
scheme is nothttps
service accounts instead of the provider's service account.
spec.parameters.kubernetesServiceAccountPath
is now ignored and will log a warning if setspec.parameters.vaultCAPem
is now ignored and will log a warning if set. This is a breaking changespec.parameters.vaultTLSClientCertPath
andspec.parameters.vaultTLSClientKeyPath
are newly available optionsIMPROVEMENTS
hashicorp/vault/api
package to communicate with Vault [GH-61]--version
flag will now print the version of Go used to build the provider [GH-62]