The last topic got auto-closed without a solution. But is a large issue for people migrating to Spaces support and trying to adopt it.
Ideally users who a Spaces admins should be able to clone a Project between two Spaces they administer. This task could either require identically named dependencies in the target Space. Or the cloned Project could just be missing Variable Sets or Tenant dependencies, and (Channel) Lifecycle dependencies could reset to default. Or for maximum bells, the dialog could list the dependencies and let users pick new ones in the target Space, or opts to remove/reset those dependencies.
In the absence of a cross-Space Clone option. In theory users should be able to use the Migration API to do roughly the same. However the page says this is not supported for Octopus Cloud, but it doesn’t say why or what the current limitation is?
Note: the migration API is not supported for migrations from self-hosted Octopus Server to Octopus Cloud currently.
Is a cross-Space Project Clone function planned for the UI?
What is the technical problem with a Migration API and Octopus Cloud? What are the operations that we should avoid and why? Can the Migration API be used at all with Octopus Cloud?