docs/redaction: document hash salting and redactSalt override#2950
Merged
Conversation
Customer question in Slack flagged that the redaction doc only mentions SHA-256 and not the salt that's appended before hashing. Update the Hash strategy description and add a new "Hashing salt" section covering automatic per-task salt management and the optional top-level `redactSalt` override on captures and derivations. Behavior reference: flow PR #2383.
|
🚀 Preview deployed to https://docs.estuary.dev/pr-preview/pr-2950/ 📄 Changed pages: |
aeluce
reviewed
May 18, 2026
aeluce
approved these changes
May 20, 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
2 participants
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.
Summary
redactSaltfield on captures and derivations as the escape hatch for customers who need to share hashed values across tasks or supply their own salt.Why
A customer asked in Slack (thread) whether Estuary supports only unsalted SHA-256 hashing, citing rainbow-table risk. The behavior in #2383 actually salts every hash and exposes a
redactSaltoverride — but features/redaction.md doesn't mention any of that today.Test plan