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
[SDBM-2635] postgres: include dbms=postgresql in SQL obfuscation options (DataDog#23926)
* [SDBM-2635] postgres: include dbms=postgresql in SQL obfuscation options
Both statement_samples.py and statements.py construct an obfuscate_options dict
from ObfuscatorOptions.model_dump() and patch in key renames (table_names,
dollar_quoted_func, return_json_metadata). The dbms field was never included,
so the Go obfuscator received DBMS="" instead of "postgresql".
While no PostgreSQL-specific tokenizer branches exist today, explicitly setting
dbms ensures parity with dbm-logs-processor and protects against future
PostgreSQL-specific lexer paths being added in go-sqllexer.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* [SDBM-2635] postgres: add changelog entry for dbms obfuscation option fix
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* [SDBM-2635] postgres: test that obfuscate_sql receives dbms=postgresql option
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* [SDBM-2635] postgres: strengthen obfuscation options test and fix changelog
- Assert directly on _obfuscate_options attributes of both classes to
unconditionally cover both code paths regardless of DB query activity
- Also assert return_json_metadata=True alongside dbms=postgresql
- Fix changelog entry missing trailing period
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* [SDBM-2635] postgres: fix line length in test_obfuscate_sql_options
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
0 commit comments