1Password api rate-limiting is extremely low

[Skarlso]

Current Behavior

Hello peeps.

External-secrets-operator maintainer here. :) We get a lot of complaints that the SDK is basically unusable because the rate-limiting is so insanely low. With connector this wasn't an issue because that cached results and secrets.

What can we do in order to improve this situation? Can you increase the rate limit or introduce caching in the SDK layer as well or is that something we ( the operator ) would have to cache on our side? ( we don't really want to because we aren't a caching layer but if that's the move, than at least it's an official stance ).

Thanks very much.

Desired Behavior

No response

Benefits & Value

No response

Additional information

external-secrets/external-secrets#4925 discussion