Censor out secret keys from backup error messages #108
houkime
commented 2024-03-18 19:56:33 +02:00
Collaborator
There is no content yet.
houkime
added 5 commits 2024-03-18 19:56:34 +02:00
b39558ea1f
fix(backups): report error in the error field of the job
b36701e31c
style(api): enable pydantic support in mypy
b40df670f8
fix(backups): censor out keys from error messages
c5b227226c
fix(backups): do not rely on obscure behaviour
continuous-integration/drone/push Build is passing
Details
houkime
requested review from inex 2024-03-18 21:08:18 +02:00
inex
approved these changes 2024-03-20 14:05:03 +02:00
houkime
merged commit 3302fe2818 into master 2024-03-20 14:18:40 +02:00
houkime
referenced this issue from a commit 2024-03-20 14:18:41 +02:00
Merge pull request 'Censor out secret keys from backup error messages' (#108) from censor-errors into master
inex
referenced this pull request 2024-04-12 17:24:32 +03:00
on fresh server, if service is not turn on, backup error #110
No reviewers
Labels
No Label
Bug
Contributions welcome
Did not do
Duplicate
Feature
Module
Backups
Module
GraphQL
Priority
High
Priority
Low
Priority
Medium
Refactor
Severity
High
Severity
Low
Severity
Medium
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: SelfPrivacy/selfprivacy-rest-api#108
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "censor-errors"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?