Getting started with 1Password for your growing team, or refining your setup? Our Secured Success quickstart guide is for you.
Forum Discussion
ftpd
3 years agoOccasional Contributor
op version two can't 'get' certain records
Hi.
I'm trying to migrate from op CLI v1 to v2, but I've encountered this problem, that some records aren't recognized.
I'm sourcing a 'script' with lines like:
export TF_VAR_some_password="...
1P_Simon
1Password Team
3 years agoHi ftpd, I'm sorry you're running into issues while migrating!
One thing that comes to mind that's also different between CLI v2 series and in v1 you had to configure accounts specifically for the CLI, independent of your accounts configured in 1Password 8. If you have the "Connect with 1Password CLI" configuration turned on, v2 will use the accounts configured in 1Password 8.
In case the item with "bad-id" is stored in an account configured in ~/.op/config
, but not in 1Password 8, that could explain the behavior you're running into.
Could you check the following to determine if you're in this situation:
1. Do you have https://developer.1password.com/docs/cli/about-biometric-unlock turned on?
2. When searching for "bad-id" in 1Password 8, do the results include the item you're looking for?
3. Does cat ~/.op/config
or cat ~/.config/op
include any accounts that are not configured in 1Password 8? Please don't paste the output here directly, or redact the entries for "accountKey". This is your secret key that only you should know.