docs: add data retention and export documentation for AI Bridge#21055
Merged
docs: add data retention and export documentation for AI Bridge#21055
Conversation
abc9827 to
d51c53d
Compare
5fef8f6 to
a63b618
Compare
dannykopping
approved these changes
Dec 2, 2025
Contributor
dannykopping
left a comment
There was a problem hiding this comment.
Awesome stuff!
Small clarification about disabling retention, which we can either add (preferable, I'm happy to do so in a precursor PR) or removed.
Thanks @mafredri
Member
Author
📚 Documentation Check✨ No Changes NeededReason: This PR already includes comprehensive documentation updates. The PR adds extensive documentation in
All user-facing changes (new This comment was generated by an AI Agent through Coder Tasks |
david-fraley
approved these changes
Dec 2, 2025
d51c53d to
58a76db
Compare
a63b618 to
68f4750
Compare
11 tasks
58a76db to
6bea198
Compare
Base automatically changed from
mafredri/feat-coderd-db-retention-policy-6
to
main
December 2, 2025 16:01
Previously AI Bridge retention was only documented in the auto-generated CLI reference, making it difficult for administrators to discover and understand how to configure data retention for compliance requirements. This adds retention configuration to the AI Bridge setup guide with examples, documents the REST API and CLI export options in the monitoring guide, and cross-references AI Bridge from the central data retention page for discoverability. Updates #21038
68f4750 to
cfabc1d
Compare
mafredri
added a commit
that referenced
this pull request
Dec 2, 2025
Previously setting AI Bridge retention to 0 would cause records to be deleted immediately since we didn't check for the zero value before calculating the deletion threshold. This adds a check for aibridgeRetention > 0 to skip deletion when retention is disabled, matching the pattern used for other retention settings (connection logs, audit logs, etc.). Also fixes the return type of DeleteOldAIBridgeRecords from int32 to int64 since COUNT(*) returns bigint in PostgreSQL. Refs #21055
mafredri
added a commit
that referenced
this pull request
Dec 3, 2025
Previously setting AI Bridge retention to 0 would cause records to be deleted immediately since we didn't check for the zero value before calculating the deletion threshold. This adds a check for aibridgeRetention > 0 to skip deletion when retention is disabled, matching the pattern used for other retention settings (connection logs, audit logs, etc.). Also fixes the return type of DeleteOldAIBridgeRecords from int32 to int64 since COUNT(*) returns bigint in PostgreSQL. Refs #21055
mafredri
added a commit
that referenced
this pull request
Dec 3, 2025
…h 0 (#21062) Previously setting AI Bridge retention to 0 would cause records to be deleted immediately since we didn't check for the zero value before calculating the deletion threshold. This adds a check for aibridgeRetention > 0 to skip deletion when retention is disabled, matching the pattern used for other retention settings (connection logs, audit logs, etc.). Also fixes the return type of DeleteOldAIBridgeRecords from int32 to int64 since COUNT(*) returns bigint in PostgreSQL. Refs #21055
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
Previously AI Bridge retention was only documented in the auto-generated
CLI reference, making it difficult for administrators to discover and
understand how to configure data retention for compliance requirements.
This adds retention configuration to the AI Bridge setup guide with
examples, documents the REST API and CLI export options in the monitoring
guide, and cross-references AI Bridge from the central data retention
page for discoverability.
Closes #20743