Fix bug where vault_kv_secret_v2
resource's cas
field had no effect
#1729
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 fixes a bug described in issue #1727. The
vault_kv_secret_v2
resource'scas
field's value was misplaced in the payload sent to Vault, failing to create or update secrets in an engine that required the check-and-set parameter.This PR also updates the resource's acceptance test by using the
cas
field. Running the test without the fix reproduces the error described in the issue.Community Note
Closes #1727
Release note for CHANGELOG:
Output from acceptance testing: