You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2023. It is now read-only.
If the user in the "vmColors" configuration leaves the body empty, then he does not want to be able to choose colors for the VM. In this case, the color selection element does not need to be output, and all current VMs should be made white.
Steps to reproduce
Set following value for "securityGroupTemplates" in config.json:
"vmColors": []
Go to the system in the VM section
Click to any VM
Click on the button to change the color of the VM
Actual result
Element for change the color of the VM is opened, but it's empty (screenshot), all VMs have retained their colors. (screenshot)
Expected result
Element for change the color of the VM is not opened, all VMs have a white color.
Environment
Browser:
- [ ] Chrome version XX
- [ ] Firefox version XX
- [ ] Safari version XX
- [ ] IE version XX
- [ ] Edge version XX
Others:
Connected feature ID
vm_colorpicker
Screenshots
The text was updated successfully, but these errors were encountered:
Description
If the user in the "vmColors" configuration leaves the body empty, then he does not want to be able to choose colors for the VM. In this case, the color selection element does not need to be output, and all current VMs should be made white.
Steps to reproduce
"vmColors": []
Actual result
Element for change the color of the VM is opened, but it's empty (screenshot), all VMs have retained their colors. (screenshot)
Expected result
Element for change the color of the VM is not opened, all VMs have a white color.
Environment
Connected feature ID
vm_colorpicker
Screenshots
The text was updated successfully, but these errors were encountered: