fix: redact database password from tracing span output [Backport release/0.5.z]#2418
Merged
Merged
Conversation
Add HideString newtype that wraps a Debug value and replaces all occurrences of a given string with "***" in the Debug output. Use it in the #[instrument] on Database::new to prevent the password from leaking through the url field in tracing spans. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> (cherry picked from commit 0bb3674)
Contributor
Reviewer's GuideBackports a fix to avoid leaking database passwords in tracing spans by introducing a generic redaction helper and applying it to the database initialization span, while wiring the new module into the common crate. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
There was a problem hiding this comment.
Hey - I've left some high level feedback:
- The
HideStringimplementation formats the entire value into aStringand then performs a replacement, which may be unnecessarily expensive for large or frequently-logged structures; consider a more targeted redaction strategy or limiting its use to small configs. - Because
HideStringuses a plain substring replacement, any occurrence of the password (even in non-sensitive fields or as part of a larger token) will be redacted; if this is a concern, you may want to constrain redaction to specific fields or more structured patterns.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- The `HideString` implementation formats the entire value into a `String` and then performs a replacement, which may be unnecessarily expensive for large or frequently-logged structures; consider a more targeted redaction strategy or limiting its use to small configs.
- Because `HideString` uses a plain substring replacement, any occurrence of the password (even in non-sensitive fields or as part of a larger token) will be redacted; if this is a concern, you may want to constrain redaction to specific fields or more structured patterns.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
helio-frota
approved these changes
Jun 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Backport of #2415 to
release/0.5.z.Summary by Sourcery
Redact sensitive database password information from tracing span output while constructing a database connection.
Bug Fixes:
Enhancements:
Tests: