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 2019/12/03 16:58:33 UTC

[GitHub] [trafficcontrol] rawlinp commented on issue #3823: Rewrite /api_capabilities to Go

rawlinp commented on issue #3823: Rewrite /api_capabilities to Go
URL: https://github.com/apache/trafficcontrol/issues/3823#issuecomment-561259691
 
 
   From my perspective I think it makes the most sense to have a plugin "seed" its own capabilities somehow on TO startup, and to not allow updating/deleting/creating capabilities at runtime. It wouldn't make sense to me to have a plugin call the `POST /capabilities` API somehow, or to have an operator `POST /capabilities` manually in order for the plugin to work. Since plugins have direct DB access already, I think they should just `INSERT` the capabilities they provide on startup (if they don't already exist).
   
   At the end of the day though, we won't really know if we have a good solution for plugin capabilities unless someone out there actually implements a plugin that uses it.

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


With regards,
Apache Git Services