kiranchavala opened a new issue, #8416:
URL: https://github.com/apache/cloudstack/issues/8416

   ISSUE TYPE
   
   Enhancement/Improvement request
   
   COMPONENT NAME
   
   Component: UI/API/
   
   CLOUDSTACK VERSION
   
   Cloudstack version 4.18
   
   SUMMARY
   
   
   Cloudstack should not allow to create resources with same name
   
   
   Currently, Cloudstack doesn't allow to creation of  the following resources 
with the same name
   
   vm name,  ssh key pairs, User-data, affinity groups, Instance groups, 
projects, accounts, Domains , users , Roles , Vpn users.
   
   For example, for vm-name it throws the following exception
   
   
   
![same-name](https://github.com/apache/cloudstack/assets/1401014/90336746-4637-4470-bf88-a66f48ecf4a8)
   
   
   
   **But Cloudstack allows the creation of the following resources with the 
same name**
   
   **volume, snapshot, template/Iso, Networks, VPC,  Service offerings, 
Kubernetes cluster**
   
   
   To maintain consistency across we should not allow to create the resources 
if there are already  active resources with the same name
   
   
   It will help the admin/user to manage the resources better
   
   
   Expected behaviour
   
   Cloudstack should validate the resource name before creating them.
   It should check if any existing active resources are present before creating 
them. 
   
   If they are present , cloudstack should throw a popup
   
   


-- 
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]

Reply via email to