I've noticed what seems to be a race condition within the CLI.
Suppose I do the following:
op get item MyItem and save the item's UUID
op create item 'Secure Note' --title=MyItem [... more parameters ...] (to enter a new version of MyItem)
op delete item UUID (to delete the original item after the new version has been created)
If immediately after step #3 I do an
op get item MyItem, I often get a listing of multiple items: the original "MyItem" and the new "MyItem".
If I wait a few seconds and re-run
op get item MyItem, I then get a proper listing of only the new "MyItem" that I created.
This seems to indicate that one or more of the three original operations were queued up in the background, even though the
op command returned with a status that said they are complete ... and this leads to a race condition.
It would be desirable if there was some way to tell the
op commands to wait and not return until the background operations are completed. I understand that this probably shouldn't be the default behavior with
op could be enhanced to take an optional
--wait command-line argument which, if present, tells it to wait for the background processing to finish.
Is this possible?
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Sync Type: Not Provided