[13.0] vault: Loosing keys when changing vault on an entry

Question

[13.0] vault: Loosing keys when changing vault on an entry

CarlosRoca13 opened this issue 2 years ago · 6 comments

TT38963

In module vault (at least in v13), when we change an entry from one vault to another existing vault, the values added on this entry cannot be accessed.

I'm not sure if this change should be allowed, if not, we should make the field readonly when it is defined to avoid this errors.

What do you think? @pedrobaeza @fkantelberg

Answer 1 · 2022-09-19T07:28:40.000Z

I think that this field should be readonly if the entry is already created.

Answer 2 · 2022-09-19T07:30:43.000Z

Readonly would be the best otherwise it's getting complicate again. If you want to move entries between vaults you can use the export -> import quite well.

Answer 3 · 2022-09-19T07:33:01.000Z

Let's go with that approach then. We can notice such thing in the known issues section and suggest Export/Import alternative. @CarlosRoca13 can you do the PR?

Answer 4 · 2023-03-19T12:11:45.000Z

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

Answer 5 · 2023-03-19T12:23:00.000Z

@CarlosRoca13 was this done?

Answer 6 · 2023-03-20T06:53:49.000Z

No, sorry, I had lost the notification between mails... 😅

I will do the change right now