Skip to content

Conversation

lena-larionova
Copy link
Contributor

@lena-larionova lena-larionova commented Sep 8, 2025

Description

Fixes #2199

  • Updated overview to mention responses
  • Added flow diagram
  • Added two examples: one for responses, and one for "both".
    • Didn't change the config of the existing example, as request mode (INPUT) is the default, so no config changes need to be made for the original config.

Preview Links

https://deploy-preview-2810--kongdeveloper.netlify.app/plugins/ai-sanitizer/
https://deploy-preview-2810--kongdeveloper.netlify.app/plugins/ai-sanitizer/examples/anonymize-request-and-response-data/
https://deploy-preview-2810--kongdeveloper.netlify.app/plugins/ai-sanitizer/examples/anonymize-response-data/

Checklist

  • Tested how-to docs. If not, note why here.
  • All pages contain metadata.
  • Any new docs link to existing docs.
  • All autogenerated instructions render correctly (API, decK, Konnect, Kong Manager).
  • Style guide (capitalized gateway entities, placeholder URLs) implemented correctly.
  • Every page has a description entry in frontmatter.
  • Add new pages to the product documentation index (if applicable).

@lena-larionova lena-larionova requested a review from a team as a code owner September 8, 2025 22:30
Copy link

netlify bot commented Sep 8, 2025

Deploy Preview for kongdeveloper ready!

Name Link
🔨 Latest commit dc80227
🔍 Latest deploy log https://app.netlify.com/projects/kongdeveloper/deploys/68c09da9b7ebfc00081531f2
😎 Deploy Preview https://deploy-preview-2810--kongdeveloper.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@lena-larionova lena-larionova force-pushed the feat/ai-sanitizer-responses branch from 55c9cfe to e51b123 Compare September 8, 2025 22:34
Copy link
Contributor

@cloudjumpercat cloudjumpercat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just had a couple suggestions!

Comment on lines 14 to 16
port:
description: The sanitizer service's port
value: $SANITIZER_SERVICE_PORT
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
port:
description: The sanitizer service's port
value: $SANITIZER_SERVICE_PORT

It's getting mad at the env var because it reads it as a string with the "", so we just have to set a placeholder

anonymize:
- all_and_credentials
sanitization_mode: BOTH
port: ${port}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
port: ${port}
port: 1111

anonymize:
- all_and_credentials
sanitization_mode: OUTPUT
port: ${port}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
port: ${port}
port: 1111

Comment on lines 14 to 16
port:
description: The sanitizer service's port
value: $SANITIZER_SERVICE_PORT
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
port:
description: The sanitizer service's port
value: $SANITIZER_SERVICE_PORT

Same issue here with the port being interpreted as a string as an env var

Comment on lines 70 to 71
1. The PII service detects sensitive data and applies the chosen sanitization method (placeholders or synthetic replacements).
1. If restoration is enabled, the plugin restores the original request data in responses before returning them to the client.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. The PII service detects sensitive data and applies the chosen sanitization method (placeholders or synthetic replacements).
1. If restoration is enabled, the plugin restores the original request data in responses before returning them to the client.
1. The PII service detects sensitive data and applies the chosen sanitization method (placeholders or synthetic replacements).
1. If restoration is enabled, the plugin restores the original request data in responses before returning them to the client.

Since I think those also apply to 3.12, I figured rather than call out each with the new_in badge, we could nest these since they're related.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This step isn't new in 3.12:

  1. If restoration is enabled, the plugin restores the original request data in responses before returning them to the client.

But the other one is. I can nest that one.

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