Hide sensitive model fields in logs
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9.9k
- Forks
- 734
- Avg merge
- 6h 36m
- Merged PRs (30d)
- 8
Description
Motivation
I'm storing sensitive values in my database that should not be exposed to the logs. When inserting data, the SeaORM query logs contain these sensitive values. I'd like to keep SeaORMs logging, as it's very convenient for development, but I still want to exclude those sensitive values from the logs.
Proposed Solutions
I could imagine an annotation on the entity column telling SeaORM not to log values for that column.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing SeaORM's query logging and entity-column configuration to determine how sensitive fields could be identified. Done means a clear, agreed approach allows logging to remain enabled while excluding values from columns marked as sensitive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100