PaulAngus commented on pull request #4200: URL: https://github.com/apache/cloudstack/pull/4200#issuecomment-905545602
> Hey, @PaulAngus I'm trying to see the risks you mention in every post on this conversation. But, at this point, I can see none. Maybe the others guys involved didn't catch that as well. > So, to clarify to us all. could please explain those risks? I'm really trying to see the damage but looks like I'm totally blind OK. So I've meant plenty of root admins who were not clear on how many aspects of how CloudStack works, Domain Admins are highly likely to have even less understanding than root admins. As it stands when a domain admin adds an offering, they are required to specify the domain to which they are adding the offering. This helps ensure that the offering is added where it was intended. There are a multitude of reasons and scenarios where a domain admin could forget/not realise/not know that the offering that they are adding would not only apply to the sub-domain that they are _thinking_ about at the time. **Increasing** the risk of inadvertent mistakes for the sake of omitting domainid=<UUID> **if** the admin is using a CLI client, does not make sense to me. And to be honest, there are so many parameters in a service offering, removing the need to define _one_ is a drop in the ocean in terms of any reduction of effort. -- 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: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
