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/09/12 17:20:48 UTC

[GitHub] [trafficcontrol] rawlinp commented on issue #3811: Rewrite /cachegroups/{{parameterID}}/parameter/available to Go

rawlinp commented on issue #3811: Rewrite /cachegroups/{{parameterID}}/parameter/available to Go
URL: https://github.com/apache/trafficcontrol/issues/3811#issuecomment-530922658
 
 
   I believe we are using cachegroup params in proprietary ways through TO extensions currently, but I am skeptical about needing the ability to check if a parameter is available to assign to a particular cachegroup. I'd think you'd start with a specific parameter, check if it's already assigned to the cachegroup, then assign it if it's not already assigned. Or, just assign the parameter without checking, and hopefully the endpoint would return a 200 saying the parameter is already assigned.

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