Sunset Passit #199
Labels
No labels
Blocked
Existing Service
Infrastructure Issue
Refactor
Security Hardening
Security Issue
Service Idea
Service Removal
Upgrade service
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: data.coop/ansible#199
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Make and announce a plan for sunsetting Passit when Vaultwarden has been set up. I'd be happy to help with a migration guide or whatever is needed.
Sunset Passitto Sunset VaultwardenSunset Vaultwardento Sunset PassitClosing this in favor of #198.
@samsapti I think this issue is distinctly about the planning and announcement to remove passit, which can be thought of as a prerequisite for removing it :)
I agree. We should have a nice migration path from passit. Since data is encrypted it'll likely require some actions from all users of passit.
It was an open service, right? Would be nice to know how many users it has to kind of set the bar.
Yes, it was (and still is) open registration. It seems the data is stored in a postgresql database. We should be able to extract user count. We can also consider extracting emails and inform users of our migration plans. WDYT?
I think that it's in the spirit of good data governance to use user's emails to inform them about important changes... SUCH AS CLOSING THE ENTIRE SERVICE 🤪