[71,72] Track item moving between vaults and requests rate limits

Are the resources you're linking to in your internal system all sign-ins or do they also include resources completely unrelated to what 1Password is offering?

We have different internal resource types, one of them is the credential type, which is basically any type of 1password item. Other internal resource types are not related. But anyway, the main problem is tracking the item when it is moved between vaults, as a moved item means a broken URL, which makes internal company processes invalid, which results in a bunch of other problems like people not knowing what to ask for, and inability to keep processes up to date (as we have hundreds of them), etc.

My first hunch would be to solve this by tracking the items ID instead of name, as the ID uniquely identifies the item independent of the vault the item is stored in.

This is was our first thought as well, BUT if you move an item to a different vault, it does change the item ID as well :) And this is the problem, so we had to implement a workaround :) I would expect such behavior from a copy functionality, but not from a move functionality.

So, if we have an item 4y72y2yklphlpjerkcgn5t7zfi in a vault mrrakx26mchefjuxcfkmoepece, we'll have this URL
https://company.1password.com/vaults/mrrakx26mchefjuxcfkmoepece/allitems/4y72y2yklphlpjerkcgn5t7zfi.

But, if we MOVE an item to a different vault, e.g. vault xny7rflfrjqasdek35zo4dssra, we'll get a totally new URL,
https://company.1password.com/vaults/xny7rflfrjqasdek35zo4dssra/allitems/something_totally_different.

This is one of the biggest problems with 1password for us, which causes us a lot of pain, unfortunately.

However, I believe moving items in 1Password is currently actually a create + delete under the hood, so the items ID will change when the item is moved. Is this why you have the workaround of storing a unique id in one of the items fields?

Yes, exactly. In a perfect world I'd not expect such a behavior.

Is using --cache an option for you?

No, it does not help. It's just caching of an item list command, but we need more data for each item, as CLI v2 item list provides only basic info. CLI v1 list items additionally provides ainfo (usually login) and URL, etc., which were kept unchanged when moving items between vaults. So, upgrading from CLI v1 to CLI v2 makes us execute 1001 commands (1 item list and 1000 item get) instead of 1 list items command when we have 1000 items (but we'll have more).

1Password API ratelimits are unfortunately not documented at this moment.

Having it not documented is fine as soon as you share the rate limit here :) So that we don't have to spend hours/days playing with that risking getting blocked for an hour each time we hit the limit.