Avoid writing empty strings to Vault when creating managed keys #1803
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.
This PR adds a fix where empty strings were being written to Vault. We should make it so that only fields provided by the user are written along with the data to Vault; if a field is not provided, empty string values should not be written. This was causing PKCS key creation to fail, since two mutually exclusive fields
slot
andtoken_label
were both being sent to Vault. The PR also adds a test that is meant to be run locally since it requires a lot of prior setup (including its own Vault server config)Fixes #1772
Output from acceptance testing: