erikbocks opened a new pull request, #12645: URL: https://github.com/apache/cloudstack/pull/12645
### Description Currently, when creating a new isolated network, it is possible to assign it as a VPC tier. The VPC assignment field is shown only when a VPC network offering is selected. However, it was noticed that VPC network offerings are listed only if the current user has at least one VPC. Otherwise, VPC network offering were not listed and it was necessary to access another account that has a VPC or create a dummy VPC. Changes were made,to list offerings based on the form selected account instead of the current user. Besides that, an warning was added below the network offerings field informing that VPC network offerings will be shown only if the selected account has at least one VPC. ### 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) - [ ] Build/CI - [ ] Test (unit or integration test code) ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [X] Minor ### Screenshots (if appropriate): Warning message: <img width="650" height="462" alt="image" src="https://github.com/user-attachments/assets/1b003c9c-8907-4f1d-ac1c-a34186af50e3"; /> <details><summary>No VPC user offerings</summary> <img width="651" height="523" alt="image" src="https://github.com/user-attachments/assets/219bc3c5-9d25-43f7-bd56-042a20d3e585"; /> </details> No warning shown for account that has a VPC: <img width="644" height="429" alt="image" src="https://github.com/user-attachments/assets/88489e4e-8342-486c-8a9c-ed6bae9e1ff1"; /> <details><summary>VPC network offerings listed for a account that has a VPC</summary> <img width="651" height="612" alt="image" src="https://github.com/user-attachments/assets/19b90fb0-9629-427f-b170-60bfc62f00a6"; /> </details> ### How Has This Been Tested? Logged in with the `admin` account, I created a VPC to the `radm` account. Then, I accessed the isolated network creation form and validated that the VPC offerings were not shown (because the current account did not had a VPC). Then, I applied the PR changes to my local environment. With the changes applied, the isolated network form was accessed again, and it was possible to see the warning message. When the `radm` was selected in the form, the warning message was hidden and the VPC offerings were listed successfully. The same tests were reproduced for projects. -- 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]
