Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
V2 rate limited for the same command used in V1
I just downloaded V2 to do testing with some already established automation that we have.
With V1 we were using the following command without any rate limiting and were able to successfully pull ...
Hey itsthecode
I believe we added 1 extra API call to improve the UX (print the vault's name) in the command. This may be the reason that the command is now hitting the rate limits (with a large enough number of vaults and items, it may be what makes the difference).
Generally in these situations, I would suggest using the --cache flag, but unfortunately the --cache flag is not supported on Windows systems.
We are currently investigating op optimizations, and part of that is reducing the number of API calls. For the time being, I regretfully can only suggest a more tedious set of commands:
op item list --categories 'CATEGORY' --vault 'VAULT OF INTEREST' | op item get - --vault 'VAULT OF INTEREST'
Specifying vault in such a way would greatly reduce the number of API calls. Specifying the vault by ID over name would further reduce the payload sizes for further optimization.
