Open adrianmoisey opened 1 year ago
This bug is still hurting us. Is there any way it can be prioritised? I made a PR but it hasn't been looked at.
Hey @benashz Sorry for the ping!
Would it be possible for someone to take a look at this issue? I did make a PR to handle it, but that went unreviewed. I'm happy to fix up that PR if needed.
Thanks.
Is your feature request related to a problem? Please describe. Some secrets (ie, AWS IAM) are eventually consistent and require a delay before they can be used.
Describe the solution you'd like A method to introduce a delay before VSO writes secrets to Kubernetes
Describe alternatives you've considered It may be possible to get the pods that consume VSO secrets to have a delay before attempting to use their secrets, but then logic needs to be build into each application. It may make sense for VSO to handle this delay, as it a central service/tool.
Additional context To quote: https://developer.hashicorp.com/vault/docs/secrets/aws#usage