Update application code to use Django 3.x #47
Merged
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.
We have been waiting with upgrading to Django
3.x
as some of the packages used, were not yet compatible.We have decided to remove the current audit logging functionality, which was provided by
django-auditlog
Additionally, we have retired
django-encrypted-model-fields
, as it had some issues with the generated encryption key on new installs. We have instead usingdjango-cryptography
instead.We will need to provide a migration path between the two libraries, as users with
2FA
enabled, will loose the configuration.If a valid migration path cannot be found, then users would need to re-enable
2FA
on their accountWith this change, we are also changing some of the terminology used, to better align with
MailScanner
.See here for related information: MailScanner/v5#492