Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Migrator does not gracefully handle importing project connections where the source project or environment does not exist in the destination #5072
Imagine a scenario where you have a mixture of projects using certain lifecycles deploying to a wide variety of environments. Now imagine you have a handful of tenants connected to a variety of those projects and environments. Finally, imagine you export one of those projects, and import it into a different Octopus Server. The tenant being migrated across is connected to a whole bunch of projects and environments which may have been exported via the partial export of a single project.
Based on how the migrator works in similar scenarios, customers expect the migrator to do its best job at merging the results together.
Today, the import process fails hard when it cannot find a mapping for an environment which a tenant is connected to.
What I expected to happen
The import process should do its best to map any projects and environments it knows about, and merge the results.
Octopus Server: 3.4 until fixed