You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My understanding is that the PII alerts produced should have trigger_type: "codegate-pii" in the JSON blob.
The task here is to:
Include PII as one of the "filter tabs"
Include PII in the summary attached to each conversation
Include PII in the "summary block" in the conversation route
Add an empty state for PII into the table's empty state component
Optional
Longer term, we will probably want to display a tab in the conversation view summarising PII discovered & redacted. However I'm not sure that we have landed on a long-term chosen design for this. The current implementation of the secrets summary is very basic and needs improving.
The concerns around this are:
The markdown is not consistent, and repeats redundant information, so it not suited to rendering in a list format
There is no structured data around secrets that is returned to be rendered in a list/table format
For PII, these constraints may also apply, I think it's open to interpretation on the best way to integrate this.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Description
Luke recently merged a PR that introduces PII protections into Codegate: stacklok/codegate#919
This should now be generating alerts when provide a file containing PII to an LLM. (See the relevant dir in the codegate-demonstration repo).
My understanding is that the PII alerts produced should have
trigger_type: "codegate-pii"
in the JSON blob.The task here is to:
Optional
Longer term, we will probably want to display a tab in the conversation view summarising PII discovered & redacted. However I'm not sure that we have landed on a long-term chosen design for this. The current implementation of the secrets summary is very basic and needs improving.
The concerns around this are:
For PII, these constraints may also apply, I think it's open to interpretation on the best way to integrate this.
Additional Context
No response
The text was updated successfully, but these errors were encountered: