[GitHub] [trafficcontrol] ocket8888 commented on issue #3870: Rewrite /capabilities to Go

2019-08-15 Thread GitBox
ocket commented on issue #3870: Rewrite /capabilities to Go URL: https://github.com/apache/trafficcontrol/pull/3870#issuecomment-521716358 The best we could do in that direction is return an error without breaking the "API version promise". And actually, that might qualify; not sure.

[GitHub] [trafficcontrol] ocket8888 commented on issue #3870: Rewrite /capabilities to Go

2019-08-15 Thread GitBox
ocket commented on issue #3870: Rewrite /capabilities to Go URL: https://github.com/apache/trafficcontrol/pull/3870#issuecomment-521713541 Oh, rob05c beat me to it. But also of note while we're looking, the Role/Capability relationship has the same problem.

[GitHub] [trafficcontrol] ocket8888 commented on issue #3870: Rewrite /capabilities to Go

2019-08-15 Thread GitBox
ocket commented on issue #3870: Rewrite /capabilities to Go URL: https://github.com/apache/trafficcontrol/pull/3870#issuecomment-521713196 > _"If you update the name of a capability does it automatically update all the FK references in the api_capabilities table?"_ It can,

[GitHub] [trafficcontrol] ocket8888 commented on issue #3870: Rewrite /capabilities to Go

2019-08-14 Thread GitBox
ocket commented on issue #3870: Rewrite /capabilities to Go URL: https://github.com/apache/trafficcontrol/pull/3870#issuecomment-521515569 1) `api_capability` links an API route to a particular capability. 2) Yes and no. We need both _concepts_, but the routes governed by a