SadiJr opened a new pull request, #6589: URL: https://github.com/apache/cloudstack/pull/6589
### Description Using the VMWare hypervisor, with the Veeam plugin active, it is not possible to remove the VM from its Backup Offering without removing its backups. To resolve this limitation, a new parameter has been added to the `removeVirtualMachineFromBackupOffering` API to allow users to disable the job but keep Veeam backups. So, when removing a VM from a Backup Offering, it is possible to pass the forced parameter to true, which will remove the job and the backups. Otherwise, the job will just be disabled and the backups will be kept. ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [x] Minor ### How Has This Been Tested? It was tested in a local lab: 1. I created a new VM and attached this VM to a Backup Offering; 2. I make some manual backups; 3. I removed this VM from the backup offering, without using the `force` option as false, and checked if, in Veeam, the job was still there, in the disabled state, and if the backups were still stored too; 4. I repeat this process, but using true in `force` option and check if the backups and job are deleted in Veeam. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
