Skip to content

Conversation

@aeluce
Copy link
Collaborator

@aeluce aeluce commented Dec 9, 2025

Description:

Adds documentation for field redaction, both for the new UI workflow and when working with specification files.

Will merge following the release of estuary/ui#1830

Documentation links affected:

Creates a new page at: https://docs.estuary.dev/security/redaction

Also updates a couple related pages to help route interested users to the redaction feature.

Notes for reviewers:

Thanks for reviewing!

@github-actions
Copy link

github-actions bot commented Dec 9, 2025

PR Preview Action v1.6.3

🚀 View preview at
https://estuary.github.io/flow/pr-preview/pr-2547/

Built to branch gh-pages at 2025-12-19 22:50 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@travjenkins
Copy link
Member

One overall thought I have here is wondering if we should leave this under security?

It 100% makes sense that if someone is reading about security they should know we allow this. However, this feels like in the long run it should live closer to other config stuff. I am initially leaning towards it being under Advanced Features and the security page is a quick landing page that links there (gross) or just redirects (also gross)

@aeluce
Copy link
Collaborator Author

aeluce commented Dec 19, 2025

Thanks for looking things over! I could certainly see it being under Advanced Features since it is a feature guide. I'll plan to move it unless anyone chimes in with other opinions.

To confirm the accuracy of the specification file section, @jgraettinger checking if this aligns with your intentions for the redaction feature? Or @jonwihl - is this basically how you instruct users to redact properties in the spec?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants