winterhazel opened a new pull request, #13213: URL: https://github.com/apache/cloudstack/pull/13213
### Description `assignVirtualMachine` demands providing a `domainid`, even though there are situations in which it is not required, such as when moving an instance to a project using `projectid`. This patch removes this restriction. ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [X] Bug fix (non-breaking change which fixes an issue) - [ ] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) - [ ] Build/CI - [ ] Test (unit or integration test code) ### Feature/Enhancement Scale or Bug Severity #### Bug Severity - [ ] BLOCKER - [ ] Critical - [ ] Major - [ ] Minor - [X] Trivial ### How Has This Been Tested? - I verified that it was possible to assign resources via the UI for both accounts and projects - I verified that it was possible to assign resources via the API by providing only the `projectid` and `virtualmachineid` parameters - I verified that it was possible to assign resources via the API by providing only the `account`, `domainid`, and `virtualmachineid` parameters - I verified that when both `projectid` and `domainid` are provided, `domainid` is ignored and the VM is moved to the project -- 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]
