[GitHub] [trafficcontrol] rob05c commented on issue #3893: Add a database constraint preventing assigning Servers from one CDN to a DeliveryService on a different CDN.

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

rob05c commented on issue #3893: Add a database constraint preventing assigning Servers from one CDN to a DeliveryService on a different CDN.
URL: https://github.com/apache/trafficcontrol/issues/3893#issuecomment-527985241
 
 
   > "[we] shouldn't hold an upgrade hostage over database state"
   
   Yeah, you're right. We do need to start marking things like this deprecated, so we can add DB constraints 2 major versions later, though.
   
   > via the API
   
   +1
   
   > Deleting data, even invalid data
   
   Er, I'm not suggesting we delete any data. Adding a constraint is good, but yes, we should never delete user data, without explicit explanation and approval.
   
   > it should be discussed on the mailing list
   
   If you all feel the need, sure. I wouldn't think an API constraint would need a discussion, I can't imagine anyone legitimately assigning DS–Servers cross-CDN. It's certainly never worked, ATS and Router config gen will fail with that in all kinds of ways. But I'm not trying to avoid a discussion, if people feel it's necessary.

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


With regards,
Apache Git Services