API Log Integrity #147
Open
API Log Integrity #147
Conversation
This file contains 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
|
Tests fail across the board due to PyYAML having dropped support for Python 3 < 3.5.0. |
|
@cyclops26 : if you would like to submit this PR into https://github.com/lingster/drf-api-tracking I can merge and deploy this for you as I've just taken up the challenge to maintain this project. |
|
@lingster Let me rebase to your fork and I will send a PR. |
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.
Added support for persistent usernames (if user model object is deleted). Added support for the log to be read-only in Django admin. Defaults are configured for full legacy support.
These are two "security" related patches that I find myself constantly backloading into projects with this package. Figured I would clean it up into something that others might find useful.