Harbor Registry Garbage Collection Execution Stall Sentinel
Audits Harbor enterprise container registry telemetry to detect stalled garbage collection jobs, lock freezes, and storage bloat.
Drives Bytebase REST API to detect failed migrations and schema drift, triggering automated schema re-sync and compensation rollback issues.
Enterprise database infrastructure governed by Bytebase requires active surveillance to ensure that database schema migrations execute smoothly and that live database instances do not diverge from version-controlled Git repositories. When concurrent transaction locks, query statement timeouts, or out-of-band manual DDL changes occur, Bytebase flags failed migration tasks and schema drift violations. This blueprint provides a native, API-driven orchestration workflow that interacts directly with Bytebase's REST endpoints: it queries active project issues and database schema snapshots, evaluates migration failures and drift metrics in Python, calls Bytebase's syncSchema API endpoint to re-align database metadata, registers an automated compensation rollback issue directly in Bytebase, and verifies the resulting database schema status.
/v1/projects/{project}/issues for failed migration issues./v1/projects/{project}/databases/{database}/schema to retrieve the active schema snapshot and drift state.If conditional task executes remediation actions directly against Bytebase APIs.:syncSchema API endpoint to trigger an immediate schema synchronization on the target database./issues endpoint to register a structured compensation rollback issue for database administrators.graph TD
Trigger[Schedule Trigger: 2h] --> FetchIssues[HTTP Request: Query Bytebase Issues]
Trigger --> FetchSchema[HTTP Request: Query Database Schema]
FetchIssues --> EvalHealth[Python Script: Parse Issues & Schema Drift]
FetchSchema --> EvalHealth
EvalHealth --> CheckRemediation{Remediation Required?}
CheckRemediation -- Yes --> SyncSchema[HTTP Request: POST databases:syncSchema]
SyncSchema --> CreateRollback[HTTP Request: POST projects/issues Rollback]
CreateRollback --> VerifyPost[HTTP Request: Query Updated Schema]
VerifyPost --> FinalLog[Log: Audit Concluded]
CheckRemediation -- No --> NominalLog[Log: Schema In Sync]
NominalLog --> FinalLog
:syncSchema endpoint to synchronize database metadata with GitOps state.| Name | Type | Default | Description |
|---|---|---|---|
bytebase_api_url |
STRING | http://bytebase.database.svc.cluster.local:8080 |
Base HTTP URL for the Bytebase database CI/CD server. |
project_id |
STRING | core-payments-db |
Identifier for the Bytebase project containing target database migration pipelines. |
database_name |
STRING | payments_production |
Logical database name evaluated for migration health and schema consistency. |
max_drift_violations |
INT | 0 |
Maximum allowable schema drift violations before triggering remediation. |
{{ outputs.evaluate_migration_and_schema_health.vars.requires_remediation }}: Boolean flag indicating if schema sync or rollback was required.{{ outputs.evaluate_migration_and_schema_health.vars.failed_issues_count }}: Number of failed migration issues detected in Bytebase.{{ outputs.evaluate_migration_and_schema_health.vars.schema_drift_count }}: Count of schema drift violations reported by Bytebase.{{ outputs.trigger_bytebase_schema_sync.statusCode }}: HTTP response status code from Bytebase schema sync invocation.{{ outputs.register_compensation_rollback_issue.statusCode }}: HTTP response status code from compensation issue creation.BYTEBASE_SERVICE_KEY.BYTEBASE_SERVICE_KEY: Service account token used to authenticate API calls against Bytebase.bytebase_api_url.BYTEBASE_SERVICE_KEY secret within your Kestra namespace settings.project_id and database name in database_name.periodic_bytebase_audit schedule trigger to establish automated surveillance.Loop task to monitor entire database clusters across multiple projects simultaneously.