You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INSERT INTO "my_super_stuff" ("my_secret_name","my_secret_key") VALUES ('toto','***')....
The idea is to let ParamsFilter handle the filtering process, but currently, it receives stmt.Vars without schema field information.
How can we associate the schema fields with stmt.Vars so that ParamsFilter can properly filter sensitive data?
Would love your thoughts on the approach and whether a PR for this feature is of interest.
Motivation
The intention is to prevent accidental exposure of sensitive data (e.g., API keys, personal information, ...) in logs. This improves security by ensuring that such values are never output, without altering the behavior of data operations.
Related Issues
None.
The text was updated successfully, but these errors were encountered:
Describe the feature
I've started work on adding support for a struct tag to exclude sensitive fields (e.g., API keys, personal information) from logs.
For example:
The idea is to let ParamsFilter handle the filtering process, but currently, it receives stmt.Vars without schema field information.
How can we associate the schema fields with stmt.Vars so that ParamsFilter can properly filter sensitive data?
Would love your thoughts on the approach and whether a PR for this feature is of interest.
Motivation
The intention is to prevent accidental exposure of sensitive data (e.g., API keys, personal information, ...) in logs. This improves security by ensuring that such values are never output, without altering the behavior of data operations.
Related Issues
None.
The text was updated successfully, but these errors were encountered: