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="...
ftpd
3 years agoOccasional Contributor
For anyone searching for similar issue in the future: 1Password Support Team was able to find a root cause of this:
"There seems to be an issue where if the user who has most recently edited an item is deleted, when 1Password CLI attempts to create the human readable version of the item info (which is done when using op item get
for all situations other than using JSON format, even if all of the human readable version is not displayed), it tries to resolve the User's UUID to get their name. Because the user that most recently edited this item no longer exists, this results in 1Password CLI being unable to resolve the user and the error is shown.
I've filed an issue internally to see if we can get this sorted out in the future."
And it matches my case - most (or even all?) of records I've checked and marked as 'not working' were created by a team member who left the company and his account was deleted from the organization. My current workaround is getting the data in JSON format and parsing them with jq
to retrieve the string I need.
Thank you Jack_P_1P, 1P_Simon and anyone else from your team involved in this ticket!