Hi. cfops restore removes the bosh-deployments.yml file by default to ensure a fresh state. This causes problems if cfops restore is used to load settings into a new Ops Manager during upgrade. The import succeeds and OpsManager shows all the tiles and VMs correctly but then attempts a fresh install when changes are applied. I think cfops should not remove this file by default. Instead a --force or similar flag could be used or simply a warning printed to the console to delete this file if you still run into problems.
Hi. cfops restore removes the bosh-deployments.yml file by default to ensure a fresh state. This causes problems if cfops restore is used to load settings into a new Ops Manager during upgrade. The import succeeds and OpsManager shows all the tiles and VMs correctly but then attempts a fresh install when changes are applied. I think cfops should not remove this file by default. Instead a --force or similar flag could be used or simply a warning printed to the console to delete this file if you still run into problems.
Thank you,