You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Jeremy Mitchell (JIRA)" <ji...@apache.org> on 2017/05/24 15:59:04 UTC

[jira] [Commented] (TC-343) TO API - add endpoint to create / delete cachegroup-parameter associations

    [ https://issues.apache.org/jira/browse/TC-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023131#comment-16023131 ] 

Jeremy Mitchell commented on TC-343:
------------------------------------

https://github.com/apache/incubator-trafficcontrol/pull/588

> TO API - add endpoint to create / delete cachegroup-parameter associations
> --------------------------------------------------------------------------
>
>                 Key: TC-343
>                 URL: https://issues.apache.org/jira/browse/TC-343
>             Project: Traffic Control
>          Issue Type: New Feature
>          Components: Traffic Ops API
>            Reporter: Jeremy Mitchell
>            Assignee: Jeremy Mitchell
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> Similar to the following api endpoints:
> POST /api/$version/profileparameters <-- create profile/parameter associations
> DELETE /api/$version/profileparameters/:profile_id/:parameter_id <-- delete profile/parameter associations
> create 2 api endpoints to do the same with cachegroup parameters such as:
> POST /api/$version/cachegroupparameters
> DELETE /api/$version/cachegroupparameters/:cachegroup_id/:parameter_id
> ^^ the interface or contact of the new apis can mirror that of the profileparameters endpoints to maintain consistency
> These functions should be limited to ops role or higher.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)