I am on 4.2.0, and i get cannot get a v2 secret with 1 or 2 set for this. Both give the same error

{"level":50,"time":1594786938370,"pid":17,"hostname":"external-secrets-do-kubernetes-external-secrets-7bcb5d65fb4qdn4","response":{"statusCode":404,"body":{"request_id":"670b25b7-36ef-8888-d214-05a09271b72e","lease_id":"","renewable":false,"lease_duration":0,"data":null,"wrap_info":null,"warnin

When specifying a vault URL, it should be possible to request round-robin discovery if the first returned vault is still sealed.

i.e.

http://vault.example.org might resolve to several addresses 10.11.11.2,10.11.11.4,10.11.11.5,10.11.11.6,10.11.11.7.

Currently if the client gets handed 1 address by DNS and it happens to be sealed, an exception is thrown. It would be convenient if the c

Description

With the changes introduced in #227, Noma API calls for job scaling operations were updated to permit stale reads. We should update the remainder of Nomad API calls for consistency and decreased load on the Nomad Servers.