Set TLS verification according to VAULT_SKIP_VERIFY #32
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.
Hi,
This is an attempt to fix the issue #31.
The difference here (when compared to
strconv.ParseBool
) is that in the original Vault implementation any other value returns an error, and here I'm keeping the default astrue
(at least for now) to avoid modifying the function's signature.I added
serial_test
to dev-dependencies to make the tests related to this feature run sequentially, and avoid one test to overwrite theVAULT_SKIP_VERIFY
value previously set by the other.Please let me know if there is anything I need to fix.