-
Notifications
You must be signed in to change notification settings - Fork 87
Docs: Add redaction feature #2547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
One overall thought I have here is wondering if we should leave this under 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 |
|
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? |
travjenkins
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has been live for a bit and docs that might not align perfectly with what people are wanting is probably better than nothing. If folks really want a change we can do that later on I guess.
lgtm
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!