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/02/08 17:31:42 UTC

[jira] [Assigned] (TC-124) Create api to queue updates on all servers for a cdn

     [ https://issues.apache.org/jira/browse/TC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremy Mitchell reassigned TC-124:
----------------------------------

    Assignee: Jeremy Mitchell

> Create api to queue updates on all servers for a cdn
> ----------------------------------------------------
>
>                 Key: TC-124
>                 URL: https://issues.apache.org/jira/browse/TC-124
>             Project: Traffic Control
>          Issue Type: Improvement
>          Components: Traffic Ops API
>            Reporter: Jeremy Mitchell
>            Assignee: Jeremy Mitchell
>            Priority: Minor
>
> Currently, you can queue updates thru the api on:
> - a server (POST/api/$version/servers/:id/queue_update)
> - a cachegroup (all servers in the cachegroup) (POST /api/$version/cachegroups/:id/queue_update)
> The TO UI allows you to queue updates on:
> - a server
> - a cachegroup (all servers in the cachegroup)
> - a cdn (all servers in the cdn)
> To obtain functional parity between the TO UI and the TO API, the following api should be created:
> POST /api/$version/cdns/:id/queue_update
> ^^ this new api should probably follow the implementation of the other 2. i.e. it should have the same request body to provide consistency.



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