ocket8888 opened a new pull request, #7718: URL: https://github.com/apache/trafficcontrol/pull/7718
Related: #5911 This PR changes the `lastUpdated` field of server objects to use RFC3339 formatting to be consistent with all of the other timestamps used by that endpoint. It also makes some other tiny naming changes for consistency within the API: `cachegroup` and `cachegroupId` are now camelCase: `cacheGroup` and `cacheGroupID`. `profileNames` is now `profiles` becasue there is no other identifying information for any Profiles on server objects from which it needs to be distinguished. `physLocation` and `physLocationId` are now actual camelCase forms of "Physical Location" and "Physical Location ID", respectively. Finally, `updPending` and `revalPending` have been removed, because they provide no information that isn't trivially calculable from other properties, and are a remnant of a legacy system. At a more implementation-detail-level, things which are never allowed to be `nil` according to API and/or database rules are now no longer allowed to be `nil` by Go's rules - because they aren't pointers anymore since they never needed to be. Also a lot of boilerplate from the method handlers was moved to a common API wrapper function. <hr/> ## Which Traffic Control components are affected by this PR? - Documentation - Traffic Ops ## What is the best way to verify this PR? Make sure the provided tests all pass. ## PR submission checklist - [x] This PR has tests - [x] This PR has documentation - [x] This PR has a CHANGELOG.md entry - [x] This PR **DOES NOT FIX A SERIOUS SECURITY VULNERABILITY** -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
