Octopus 3.0 - Migrator RFC
Blog post from Octopus Deploy
Octopus Deploy's transition from version 2.6 to 3.0 involves a significant shift from using RavenDB to SQL Server, necessitating a comprehensive data migration tool that also functions as a general exporter and importer for Octopus 3.0. This migration tool supports various scenarios such as importing data from 2.6 into 3.0, exporting and re-importing data within 3.0 servers, and merging or splitting data across multiple 3.0 servers. The exported data, focused on configuration elements like projects and environments, is stored as JSON files, which can be committed to a Git repository or transferred to new servers. Importing allows for data preview and conditional overwriting or skipping of existing documents, with transaction safety ensured by rolling back changes if issues arise. While exporting and importing historical data like deployments and audit events is initially unsupported, there are plans to incorporate this feature, particularly for importing history from 2.6 backups. The company seeks feedback on the importance of handling historical data in version 3.0, aiming to prioritize user needs effectively.