feat(mt#528): Deprecate and remove sessiondb configuration block#162
Open
feat(mt#528): Deprecate and remove sessiondb configuration block#162
Conversation
- Create configuration migration utility to convert sessiondb: to persistence: - Add config migrate command with dry-run, backup, and validation options - Enhance deprecation warnings in persistence service and CLI utilities - Update core documentation examples to use persistence: configuration - Create comprehensive deprecation timeline with phased approach Key features: - Automatic configuration detection and migration - PostgreSQL and SQLite backend support with proper schema mapping - Backward compatibility during transition period - Clear deprecation warnings with migration instructions - Extensive validation and error handling Closes: mt#528
- Consolidate multi-line log.warn calls for better readability - Update documentation formatting - Minor code style improvements
- Resolved conflict in formatting-utilities.ts by combining deprecation warnings with persistence display logic - Includes migration utility, deprecation warnings, documentation updates, and configuration migration timeline
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
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.
Implement sessiondb to persistence configuration migration
This PR implements a comprehensive migration system to deprecate the legacy
sessiondb:configuration in favor of the modernpersistence:configuration, completing the configuration unification started in mt#407.Summary
Provides a complete migration path from legacy
sessiondb:configuration to the new unifiedpersistence:configuration, with backward compatibility, clear deprecation warnings, and comprehensive tooling.Changes
Added
Configuration migration utility (
src/utils/config-migration.ts)sessiondb:blocks topersistence:blocksminsky config migratecommand (src/commands/config/migrate.ts).minsky/config.yaml, etc.)Comprehensive deprecation timeline (
docs/sessiondb-deprecation-timeline.md)Changed
Enhanced deprecation warnings in
PersistenceServiceand CLI utilitiessessiondb:configuration is detectedUpdated documentation to use
persistence:configuration examplesdocs/configuration-guide.md- Updated CLI examples and environment variablesdocs/repository-configuration.md- Migrated all configuration examplesConfiguration Mapping
Before (legacy)
After (modern)
Testing
Usage
Breaking Changes
None - this is a pure addition with full backward compatibility. Legacy
sessiondb:configurations continue to work with deprecation warnings.Migration Timeline
Closes mt#528