You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2018/12/20 23:05:26 UTC

[GitHub] rawlinp commented on issue #3107: /api/1.3/origins has bad interactions with STEERING Delivery Services

rawlinp commented on issue #3107: /api/1.3/origins has bad interactions with STEERING Delivery Services
URL: https://github.com/apache/trafficcontrol/issues/3107#issuecomment-449164738
 
 
   This is not really a problem with just the Origins API. For any endpoint that returns read-only fields (usually name fields like `profileName`, `fooName`, etc.), you can pass a value for those in a PUT/POST request, and the API will return back the value you requested in the response. However, a subsequent GET will contain the _correct_ things in those read-only fields because they will actually be populated with a SQL SELECT statement. The problem is that most of our traffic_ops_golang APIs don't properly populate those read-only fields to return in POST/PUT response by doing a SQL SELECT after doing the SQL INSERT/UPDATE. Ideally this would be fixable in the framework rather than requiring changes on a per-handler basis.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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