Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Hi team, I'm using OCI object storage in production, and I found it returns 403 or 404 when temporary authentication failures.
For now, we only retry limited error status, and there's no way for us to customize our retry policy; for my case specially, I do want to retry on 403/404.
Describe the solution you'd like
Make retry policy a functor, so users could customize their own retry logic; meanwhile default policy shouldn't be changed.
Describe alternatives you've considered
There're some well-known retry libraries on the market, like backon, we could also adopt it as well.
Additional context
I'm discussing with OCI team on the HTTP status code, but would like to have customized retry policy to unblock.
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Hi team, I'm using OCI object storage in production, and I found it returns 403 or 404 when temporary authentication failures.
For now, we only retry limited error status, and there's no way for us to customize our retry policy; for my case specially, I do want to retry on 403/404.
Describe the solution you'd like
Make retry policy a functor, so users could customize their own retry logic; meanwhile default policy shouldn't be changed.
Describe alternatives you've considered
There're some well-known retry libraries on the market, like backon, we could also adopt it as well.
Additional context
I'm discussing with OCI team on the HTTP status code, but would like to have customized retry policy to unblock.