Getting a 409 error calling op-connect from Terraform
We're using Terraform to read and provision 1password secrets, via op-connect.
op-connect container version: 1.6.1
terraform 1password module version: 1.2.0
We use Terraform to provision various resources from cloud services, including 1Password.
When doing only reads of 1password resources, all works fine. When doing a single write, all is fine.
However, when an apply requires two or more create/update operations, only the first will succeed. The subsequent ones return:
��� Could not update item 'xxxxx' from vault
��� 'yyyyy', got error: status 400: Network: (DB: (409)
��� (Conflict), Internal server conflict.), DB: (409) (Conflict), Internal
��� server conflict.
Re-running the apply will make the second one apply correctly, and so on.
This seems to be some sort of rate limit, or incompatibility with the way Terraform works (TF will read current status, build an apply plan, and then apply the actions). There is another thread here with someone experiencing something very similar using Ansible.
Is this a known bug, or is there a recommended way to configure for this? Will the problem go away if we move to using Service Accounts (IE, is the problem with op-connect rather than 1Password itself)?
1Password Version: 2.30
Extension Version: Not Provided
OS Version: Linux
Browser: Not Provided