Currently, rate limits are absurdly low for service accounts (IMO) if you plan on pulling multiple items on every terraform plan/apply.
Caching could help us get around this.
Use cases
If you pull 20 items in your terraform project, this means that you can run terraform plan/apply at most 50 times per 24h period on the 1Password and 1Password Families plan (since they have a limit of 1000 read/write per 24h period).
Proposed solution
Implementing a caching system or making a per-item age-before-refresh configuration may allow us to significantly reduce the number calls.
Summary
Currently, rate limits are absurdly low for service accounts (IMO) if you plan on pulling multiple items on every terraform plan/apply. Caching could help us get around this.
Use cases
If you pull 20 items in your terraform project, this means that you can run
terraform plan/applyat most 50 times per 24h period on the 1Password and 1Password Families plan (since they have a limit of 1000 read/write per 24h period).Proposed solution
Implementing a caching system or making a per-item age-before-refresh configuration may allow us to significantly reduce the number calls.
Is there a workaround to accomplish this today?
None that I know of.
References & Prior Work
N/A