Development#16
Merged
Merged
Conversation
Fully tested end to end MigrationOps dashboard. Shipped features: - Failure logging (MigrationOps.Core): __MigrationHistory now has Success/ErrorMessage/DurationMs columns, added via a safe in-place ALTER TABLE for databases that already have the old table — verified this upgrade path against a simulated pre-existing table. A failed migration no longer just prints to console and vanishes; it's recorded, and doesn't block retry on the next run (verified: broke a migration, saw it logged as a failure, fixed it, saw it retry and succeed). - Failure alerts: a generic webhook fires on failure (AlertSettings in dbconfig.json), verified against a real local listener — correct JSON payload, and a dead webhook URL doesn't crash the migration run. - Dashboard (MigrationOps.Dashboard, new project): Overview (stat tiles), per-database detail (history + pending + checksum-drift detection), and a filterable History page. Cookie auth with first-run-only self-registration (not open signup), separate dashboard-only user store, BCrypt-hashed passwords — all screenshotted and working in both dark (default) and light themes. - Found and fixed one real gap along the way: the dashboard would have crashed on any migration file that hasn't been through the checksum pre-commit hook yet (a normal in-progress state); it now shows those as a distinct "Draft (no checksum)" badge instead.
Fully tested end to end MigrationOps dashboard. Shipped features: - Failure logging (MigrationOps.Core): __MigrationHistory now has Success/ErrorMessage/DurationMs columns, added via a safe in-place ALTER TABLE for databases that already have the old table — verified this upgrade path against a simulated pre-existing table. A failed migration no longer just prints to console and vanishes; it's recorded, and doesn't block retry on the next run (verified: broke a migration, saw it logged as a failure, fixed it, saw it retry and succeed). - Failure alerts: a generic webhook fires on failure (AlertSettings in dbconfig.json), verified against a real local listener — correct JSON payload, and a dead webhook URL doesn't crash the migration run. - Dashboard (MigrationOps.Dashboard, new project): Overview (stat tiles), per-database detail (history + pending + checksum-drift detection), and a filterable History page. Cookie auth with first-run-only self-registration (not open signup), separate dashboard-only user store, BCrypt-hashed passwords — all screenshotted and working in both dark (default) and light themes. - Found and fixed one real gap along the way: the dashboard would have crashed on any migration file that hasn't been through the checksum pre-commit hook yet (a normal in-progress state); it now shows those as a distinct "Draft (no checksum)" badge instead.
…vice The remote dashboard branch and the local dashboard commits had both diverged and neither side's MigrationService.cs compiled. Resolved by combining the modern apply pipeline (transactional apply + history insert, object-script deferral, config layering) with the dashboard additions: alert notifier, config-path constructor, GetDatabaseNames, GetMigrationHistory, GetMigrationFileStatuses, and the extended __MigrationHistory schema (Success/ErrorMessage/DurationMs). Failed migrations now record a Success = 0 history row and fire the webhook without masking the original error. Removed the broken RecordMigration and HasMigrationBeenApplied fragments and duplicated method copies. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Feature/migrationops dashboard
Add details on first run, user setup, configuration and dashboard features.
…est-updates Update README
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Merge dev into main