feat: add database purge for old provisioner job logs and timings #18744
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.
Summary
This PR implements a database purge feature for old provisioner job logs and timings to help manage database storage growth.
Changes
Database Migration
000347_workspace_builds_purged_at
to add apurged_at
column to theworkspace_builds
table for tracking purged buildsSQL Queries
DeleteOldProvisionerJobLogs
andDeleteOldProvisionerJobTimings
queries inprovisionerjobs.sql
Database Purge Integration
dbpurge.go
to call the new deletion methods with a 90-day thresholdTesting
TestDeleteOldProvisionerJobLogsAndTimings
Generated Code Updates
dbmock
to include new methodsdbmetrics
packageTesting
The implementation has been thoroughly tested:
Impact
This feature will help reduce database storage usage by automatically cleaning up old provisioner job logs and timings while preserving important recent data and the latest build information for active workspaces.