`op account add` with `Integrate with 1Password CLI`
We have a significant amount of automation around `op`, we use a shared service account (not a service account token, a real 1password account with an email and a secret key) to do perform this automation.
We occasionally need to run this automation from developer machines and recently noticed that some developers had `Integrate with 1Password CLI` enabled.
This had several effects that caused our automation to do the wrong thing.
Our automation starts by doing `op account add --address=… --email=… --secret-key=… --signin --raw` which is expected to print a session token to stdout.
We then pass that session token back to `op` with `--session`.
However when this is run on a machine with `Integrate with 1password CLI` enabled, `op account add` prints the following message to stderr:
1Password CLI is now connected with the 1Password app. Add an account through the 1Password app.
To learn how to add an account to the 1Password app, visit: https://support.1password.com/add-account
And exits with an exit code of `0`.
At this point our automation believes it has a valid session for the account it tried to add and we pass that session w/ `op --session` to all future operations.
However the `--session` argument appears to be completely ignored if the 1password app integration is enabled, so it will actually perform actions using the account from the developer's 1password app.
This causes some operations (such as creating vaults) to succeed but for permissions to access and manage the vault to be incorrect.
There does not appear to be any way for our automation to override or bypass the 1password app integration from the CLI.
Ideally it would be possible for us to force the 1password CLI to not use the app integration in this case, however it'd also be good if `op account add` didn't exit with a code of `0` in this case, since it was not able to add the account.