Yes, when modifying a DS, it would be useful to have an API to queue on just servers relevant to that DS.
—Eric > On Jan 31, 2017, at 12:36 PM, Jeremy Mitchell <[email protected]> wrote: > > Currently, you can queue updates: > > - for a specific server > - for a specific cachegroup (all the servers in that cachegroup) > - for a specific cdn (all the servers in that cdn) > > but you can't queue updates for: > > - a specific delivery service (all the servers explicitly (edges) or > implicitly (mids) assigned to that DS) > > Does it make sense to add this functionality? At least to the API? > > I "think" when a delivery service change is made, it is common practice to > queue updates on the ENTIRE cdn that the DS belongs to. This seems like it > would unnecessarily queue updates for a lot of servers that don't belong to > the DS. > > I know we may move away from the queue update approach at some point but > does this functionality make sense in the short term? > > Jeremy
