rob05c opened a new issue #4751: URL: https://github.com/apache/trafficcontrol/issues/4751
A lot of the error and warning logs in the Config Gen (`lib/go-atscfg` and `traffic_ops/ort/atstccfg`) are data errors. We should go thru all the log lines, identify which ones are data errors, and then add code to the Traffic Ops API Validation, to disallow PUT and POST requests which result in invalid configuration. This would make Traffic Control much safer, easier to operate, and eliminate "footguns," to make all these errors impossible. ## I'm submitting a ... - [ ] bug report - [x] new feature / enhancement request - [ ] improvement request (usability, performance, tech debt, etc.) - [ ] other <!--(Please do not submit support requests here - see above)--> ## Traffic Control components affected ... - [ ] CDN in a Box - [ ] Documentation - [ ] Grove - [ ] Traffic Control Client - [ ] Traffic Monitor - [x] Traffic Ops - [ ] Traffic Ops ORT - [ ] Traffic Portal - [ ] Traffic Router - [ ] Traffic Stats - [ ] Traffic Vault - [ ] unknown ## Current behavior: Currently, lots of invalid config state is possible via missing and invalid data, which will result in ATS configuration failure. ## Expected / new behavior: Traffic Ops API rejects modification requests which result in invalid cache config, as much as possible. ## Minimal reproduction of the problem with instructions: Countless possible errors. Trivial example? Delete a DS Location Parameter for Header Rewrite. ## Anything else: ---------------------------------------------------------------- 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]
