Correctly handle 404 response in approle secret id request #1242
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.
After hashicorp/vault#12788 was merged and released in 1.9.0, the
role/:name/secret-id-accessor/lookup
vault server endpoint now returns a 404 status code when the secret_id_accessor cannot be found. This breaks the vault_approle_auth_backend_role_secret_id resource, which will always return an error if 404 is returned.This PR fixes this issue.
Community Note
Closes #1241
Release note for CHANGELOG:
Output from acceptance testing: