[GitHub] [trafficcontrol] rob05c edited a comment on issue #5893: Snapshotting a CDN that has an HTTPS delivery service w/ no cert causes TR crconfig reload failure

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

rob05c edited a comment on issue #5893:
URL: https://github.com/apache/trafficcontrol/issues/5893#issuecomment-849175908


   I vote for both [1] or [2] (I don't have a strong opinion which), and [3]. Robust systems require multiple failsafes. I know we have limited resources, but config loading (on both TR and Caches) is a particularly dangerous part of our system. 
   
   We should have validation in TO and/or TP, and TR and ATS should also detect and refuse to apply changes to a single DS that they recognize is invalid, but still apply changes for every other DS.
   
   This is especially necessary for Self-Service, to catch tenants who mash keys until something broken slips thru one validation. To make the CDN keep working and applying changes for every other tenant.
   
   On the UI Usability side, we should also fix the chicken-and-egg problem, so it's possible to fully create the DS at once, and not necessary to create temporary wrong config in order to get to the final config.


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