Signing back into the Community for the first time? You'll need to reset your password to access your account.  Find out more.

Forum Discussion

austin's avatar
austin
Occasional Contributor
3 years ago

Problems with op v2 when integrating with chezmoi

I’ve recently upgraded to op v2, and it’s breaking chezmoi fairly hard. Even if the first issue is fixed (either in op or in chezmoi), there appear that there will be different errors based on whethe...
CLI
Former Member's avatar
Former Member
3 years ago

Hey austin,

Thank you for reaching out to us. Let's address these issues in order:
1. op signin signature has changed - this has been done so by design. While all the other commands accepted the account filter through a flag, op signin was the odd one out. This change came, in our opinion, to ensure consistency and intuitivity in the CLI, between different commands.
2. session token name changed - We tried, as much as possible, not to make this a breaking change. While OP_SESSION_<account_id> is now set in the environment instead of OP_SESSION_<shorthand>, the CLI actually fetches the token from the latter envvar as well, if it cannot find the first one. Can you please elaborate a bit on your use-case here?
3. Indeed, no OP_SESSION_*. You can find more details about biometric unlock here: https://developer.1password.com/docs/cli/biometric-security#technical-design
4. Different response for op account list --format json - within biometric unlock, there is no such concept as an account shorthand. You can indeed use the first part of your sign-in address as an account filter, but that is different from an account shorthand. To state one difference, the user cannot modify that via the CLI.

I get the feeling that there may be more questions within your messages, so please, do follow up and let us know how can we help you further!

Best,
Horia