Is your feature request related to a problem? Please describe.
The same way Cyclops UI supports migrating releases in a batch, cyctl should be able to migrate releases in modules.
cyctl should take a list of modules that need to be migrated and retain the values each release had. While doing the batch migration, values should not be changed during a migration the way its possible while migrating a single release
Is your feature request related to a problem? Please describe.
The same way Cyclops UI supports migrating releases in a batch,
cyctlshould be able to migrate releases in modules.cyctlshould take a list of modules that need to be migrated and retain the values each release had. While doing the batch migration, values should not be changed during a migration the way its possible while migrating a single release