Request: Retry mechanism for vault template

[worldtiki]

Hi 👋

I saw this first asked in stackoverflow.

This seems fairly common and a normal thing to have (retries) but all the alternatives to implement this are very cumbersome.
With the advent of service meshes I believe this will become even more necessary as a common issue when using these are race conditions between our Spring application and the service mesh proxy which can cause the Spring app to fail to start.

I think having something like spring.cloud.vault.something.retries=3 would be a more convenient way to do this and a much welcomed feature by users of Spring Vault.

I'm happy to draft a pr if there is interest.

[kgunnerud]

Would be neat.

From time to time, we get a ConnectionReset or something similar, which does not pose a problem since its the health check, but as we have metrics on health checks this creates an alert. Network faults will happen, although not often. So having some kind of retry on operations that leave your application would not be totally insane?