[v5.x] feat(cloud): user and team inactivity management#9873
Open
peaklabs-dev wants to merge 5 commits intonextfrom
Open
[v5.x] feat(cloud): user and team inactivity management#9873peaklabs-dev wants to merge 5 commits intonextfrom
peaklabs-dev wants to merge 5 commits intonextfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I am overall not the biggest fan of inactivity tracking on services where the service sends you an email or deletes your account after 6 months of inactivity for example. So core Coolify will not have inactivity tracking in general.
However, as we are migrating all database data from v4 to v5 during the upgrade migration, for this one isolated case (the migration) it makes sense to not migrate over inactive users and teams. This will speed up migration, clean up the v5 databases and also save disk space.
Changes
ended_atcolumn to subscriptions tableended_aton cancellations, expirations or refundsended_atfor past subscriptionsNote: This command is intended to only be run 30 days from the scheduled upgrade migration to v5 on the cloud version, not before
This is part 1 of 2 in a stack made with GitButler: