Lj 462 Reduce Logging for Disabled Cache on SQLAlchemy

[Vagoasdf]

Closes LJ#462

Description Of Changes

We were having trouble with unwanted SQLAlchemy log message related to caching issues with third-party dialects like Redshift.

Code Changes

• Implemented a SQLAlchemyGeneratedFilter in sqlalchemy_filter.py to filter out specific unwanted log messages from the SQLAlchemy engine. (Thanks @galvana )
• Added a new test suite TestSQLAlchemyLogger in test_logger.py to ensure that the SQLAlchemyGeneratedFilter correctly filters out unwanted log messages.

Steps to Confirm

1. Run the test suite in test_logger.py to ensure that the SQLAlchemyGeneratedFilter is correctly filtering out the specified log messages.

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fides-plus-nightly	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 25, 2025 9:22pm
fides-privacy-center	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 25, 2025 9:22pm

[codecov]

Codecov Report

Attention: Patch coverage is 93.75000% with 1 line in your changes missing coverage. Please review.

Project coverage is 86.93%. Comparing base (7a5def5) to head (6126e5a).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/fides/api/util/sqlalchemy_filter.py	91.66%	0 Missing and 1 partial ⚠️

❌ Your patch status has failed because the patch coverage (93.75%) is below the target coverage (100.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6089   +/-   ##
=======================================
  Coverage   86.92%   86.93%           
=======================================
  Files         420      421    +1     
  Lines       26027    26043   +16     
  Branches     2833     2836    +3     
=======================================
+ Hits        22625    22640   +15     
  Misses       2787     2787           
- Partials      615      616    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[JadeCara]

How certain are we that these are the only caching related substrings we need to catch? Are there any other substrings related to PII we might want to guard against (that may or may not be happening now?)

[Vagoasdf]

The one we detected during this Issue was related to caching strategies for third party dialects. Docs over here: https://docs.sqlalchemy.org/en/14/core/connections.html#engine-thirdparty-caching point to the following structure for this error

For all third party dialects that don’t support this attribute, the logging for such a dialect will indicate dialect does not support caching.

cached since and caching disabled are failsafe nets for similar error that might contain PII, but haven't showed on the logs yet

[JadeCara]

The tests work for all test cases. I had one question about if we are filtering strongly enough, but this will definitely solve the immediate problem. Approving.

[cypress]

fides    Run #12881

Run Properties:   Passed #12881  •  5b0b7de260: Lj 462 Reduce Logging for Disabled Cache on SQLAlchemy (#6089)

Project	fides
Branch Review	main
Run status	Passed #12881
Run duration	00m 54s
Commit	5b0b7de260: Lj 462 Reduce Logging for Disabled Cache on SQLAlchemy (#6089)
Committer	Bruno Gutierrez Rios
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	0
Skipped	0
Passing	5
⚠️ You've recorded test results over your free plan limit. Upgrade your plan to view test results.
View all changes introduced in this branch ↗︎