Moving linked items between vaults
We have a lot of items that are stored as linked items with documents in a shared vault. Access to a subset of these items must be more restrictive for regulatory reasons, so we need to move them to a new vault.
I understand that links cannot span vaults, but IMO there is no technical reason why 1P shouldn't be able to copy over the password and document entries and afterwards reconstruct the links. All the information is there. But still, it only warns that the links will be severed and offers two options that are both worthless to me (Cancel or accept the broken links).
Happy as I am with 1Password, this feature has been sorely missing ever since the introduction of the hosted model. At the beginning I was willing to think that it would certainly be coming soon. However, I am not so sure anymore. Are there any plans to implement this? Judging from the number of people asking about this here in the forum it should be high on the list.
As long as it is not there, any suggestions on how to automate this, maybe with the CLI tool?
1Password Version: 7
Extension Version: Not Provided
OS Version: macOS 10.13
Sync Type: 1Password for Teams
Comments
-
Hi @dschneller
Are there any plans to implement this?
Unfortunately I'm not aware of any definite plans at this point. It is on the wish list, but I couldn't say for sure when/if this will be possible.
As long as it is not there, any suggestions on how to automate this, maybe with the CLI tool?
Hmm. The CLI tool may be able to help, but I don't know off-hand how. I'll ask someone more familiar to chime in here.
Ben
0 -
Any word from someone more familiar?
0 -
Hey @dschneller I'm one of the CLI devs. We don't have explicit support for links in the CLI, but if you inspect the JSON of some of your items with
op get item, you should be able to re-create them in a new vault withop create itemand some scripting magic. Please let me know if you have any questions about how to get started.0 -
Yeah... I figured as much... And it seems that's my only option unless I want to spend a few days repairing links UI wise.
Even though I am confident I will be able to get it working in the end, it will (and can!) only be a dirty hack: AFAICT there is no public and binding documentation of the JSON format, so I must assume that you guys will at any point in the future break whatever scripts I concocted, potentially without my script even failing, but corrupting data.
IMO implementing this on your side would be much simpler; all the data that I now have to effectively reverse engineer trough trial and error is already there on your side. And, of course, you can also make sure to keep the code in line with any future data structure changes.
So in the end, I must say, I am very disappointed that what I consider a quite basic feature is not there. I am reluctant to believe that moving linked things between vaults should be an unusual use case. Especially with links being explicitly marketed as an advantage to the older idea of attachments.
0 -
Let me add that even once I managed to script this, the performance will be horrible.
This is a typical response time, from what I can tell:$ time op get item someuuid op get item someuuid 0.87s user 0.23s system 32% cpu 3.385 total
More than 3 seconds for a single get item call --- let alone following all the potential links and creating items....
Even when fully automated, with the number of items I want to move at the moment, I am looking at potentially hours of run time.
Not happy... very not happy...0 -
IMO implementing this on your side would be much simpler
I don't know if I can agree that it would be simpler, but I do agree it would be better. We'd certainly like to do this, but there are only so many hours in the day. I'll happily pass your feedback along to the rest of the team and hopefully this is something we can tackle in a future update.
Ben
0 -
@dschneller You're entirely correct we should be handling this use case better. Especially in the CLI; however the tool is still in beta, as we are still adding functionality to it. Managing links is certainly something we want to support in the future, but at the moment we are focused on automating administrative features. I've brought this up with my team to discuss any possible better solutions.
0 -
Just noticed one more thing which I consider quite serious: When moving linked items between vaults with the "Move To" context menu item, I get the two alert sheets (Confirm Move, Warning: Links will be broken).
When I drag and drop the two selected items to a vault in the sidebar, the move happens without any UI changes (no confirmation, no warning). So this silently severs the link, which is pretty bad, because when you do that with a lot of items with similar names, you are in for a world of pain when you notice, potentially sometime in the future.
0 -
Good observation @dschneller.
Ben
0
