feat: remove persons with cronjob when retention period has exceeded#409
Merged
Conversation
Contributor
|
KULTUS-API branch is deployed to platta: https://kultus-pr409.api.dev.hel.ninja 🚀🚀🚀 |
nikomakela
force-pushed
the
PT-1932-cronjob-delete-persons
branch
from
e249963 to
d1dd17d
Compare
Contributor
|
KULTUS-API branch is deployed to platta: https://kultus-pr409.api.dev.hel.ninja 🚀🚀🚀 |
nikomakela
force-pushed
the
PT-1932-cronjob-delete-persons
branch
from
d1dd17d to
499ed73
Compare
Contributor
|
KULTUS-API branch is deployed to platta: https://kultus-pr409.api.dev.hel.ninja 🚀🚀🚀 |
PT-1932. The `delete_retention_period_exceeding_contact_info` cronjob has deleted contact info from PalvelutarjotinEvent when the retention period (48h) has exceeded, but the persons have been deleted manually from the enrollee personal data admin view. Since it's been a manual task, it has always needed some one to take care of it. There is no reason why that job could not be done automatically with a cronjob. The `delete_retention_period_exceeding_contact_info` cronjob is now extended with that feature, but there are also new flags that can be used to run only 1 of the tasks (with the management command that the cronjob executes) and tehre is also a flag to make a dry drun, that does not acutally delete anything, but just reports how many instances it would delete if it would be ran.
nikomakela
force-pushed
the
PT-1932-cronjob-delete-persons
branch
from
499ed73 to
03ba0ab
Compare
|
Contributor
|
KULTUS-API branch is deployed to platta: https://kultus-pr409.api.dev.hel.ninja 🚀🚀🚀 |
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
2 participants
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.
PT-1932.
The
delete_retention_period_exceeding_contact_infocronjob has deleted contact info from PalvelutarjotinEvent when the retention period (48h) has exceeded, but the persons have been deleted manually from the enrollee personal data admin view. Since it's been a manual task, it has always needed some one to take care of it. There is no reason why that job could not be done automatically with a cronjob.The
delete_retention_period_exceeding_contact_infocronjob is now extended with that feature, but there are also new flags that can be used to run only 1 of the tasks (with the management command that the cronjob executes) and tehre is also a flag to make a dry drun, that does not acutally delete anything, but just reports how many instances it would delete if it would be ran.