[GitHub] [trafficcontrol] ocket8888 edited a comment on issue #5218: Add delivery service server assignment safeties to Traffic Ops

[GitBox <gi...@apache.org>]

ocket8888 edited a comment on issue #5218:
URL: https://github.com/apache/trafficcontrol/issues/5218#issuecomment-725591018


   I like to think of these things not in terms of API endpoints and alerts and restrictions - those are just implementation details - but in terms of the data model. "An Active Delivery Service cannot be made un-serviceable" seems reasonable, and so I agree with Rawlin. We could _also_ issue warnings for low-server-count DSes, but the point here is to restrict the supported data sets/operations to disallow more that cannot possibly work.
   
   Also, though, I think "An active Delivery Service must be serviceable" also makes sense, which is a different issue, but maybe people shouldn't be allowed to create active Delivery Services and not allowed to set a DS active if it has no assigned servers/topology?


----------------------------------------------------------------
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:
users@infra.apache.org