While working on VSO, we discovered an issue where a read on non-existent mount resulted in an error that prevented the provider from completing successfully.
This PR reworks the error handling for both auth and secret engines.
Additional fixes:
CI: test against vault enterprise 1.17.1; drop 1.11.x
╷
│ Error: error reading from Vault: Error making API request.
│
│ URL: GET http://127.0.0.1:8200/v1/sys/mounts/auth/demo-auth-mount
│ Code: 400. Errors:
│
│ * No secret engine mount at auth/demo-auth-mount/
│
│ with vault_auth_backend.default,
│ on auth.tf line 5, in resource "vault_auth_backend" "default":
│ 5: resource "vault_auth_backend" "default" {
│
While working on VSO, we discovered an issue where a read on non-existent mount resulted in an error that prevented the provider from completing successfully.
This PR reworks the error handling for both auth and secret engines.
Additional fixes:
See sample error below for https://github.com/hashicorp/vault-secrets-operator/blob/8ee1ba05f08ea1c74a3cdcc76653908a8ae7f46f/demo/infra/app/auth.tf#L5 :
The issue seems to also lead to the https://github.com/hashicorp/vault-secrets-operator/actions/runs/9810145898/job/27089804738#step:3:6485