PaulAngus commented on pull request #4200: URL: https://github.com/apache/cloudstack/pull/4200#issuecomment-740132818
That's simple. With service offerings, you both protect the infra and set what the users can do within that infra according to your use case. What anyone can do WITHIN those bounds will be fine, assuming that the bounds were set correctly. Therefore it is essential that the service offerings and their coverage is spot-on. Mistakes there could cause real problems. You're taking away a safety net and you're not adding something that domain admins couldn't do if they passed the domain id in the first place. It looks to me that you want to make it easier for admins to get in a car by removing all of the locks. But it's not worth this amount of energy to keep arguing. So someone can merge this if they want. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
