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 2020/10/05 17:22:18 UTC

[GitHub] [trafficcontrol] zrhoffman opened a new issue #5099: Validate topology field on PUT /deliveryservices with respect to required capabilities

zrhoffman opened a new issue #5099:
URL: https://github.com/apache/trafficcontrol/issues/5099


   <!--
   ************ STOP!! ************
   If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact
   the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
   guidelines at https://www.apache.org/security/ regarding vulnerability disclosure.
   
   - For *SUPPORT QUESTIONS*, use the Traffic Control slack (https://s.apache.org/atc-slack)
   or Traffic Control mailing lists (https://trafficcontrol.apache.org/mailing_lists).
   - Before submitting, please **SEARCH GITHUB** for a similar issue or PR.
   -->
   
   ## I'm submitting a ...
   <!-- delete all those that don't apply -->
   <!--- security vulnerability (STOP!! - see above)-->
   -  improvement request (usability, performance, tech debt, etc.)
   
   ## Traffic Control components affected ...
   <!-- delete all those that don't apply -->
   -  Traffic Ops
   
   ## Current behavior:
   <!-- Describe how the current features are insufficient. -->
   We do not have validation on `PUT /api/3.0/deliveryservices/:id` when the DS has a topology and the DS has required capabilities.
   
   ## New behavior:
   <!-- Describe how the feature would improve Traffic Control -->
   As a CDN operator, I'd like ensure that the topology I've chosen for my delivery service is valid w.r.t its required capabilities.
   
   Each cachegroup in the assigned Topology should contain at least one server (in the delivery service's CDN) with the delivery service's required capabilities, otherwise the request should fail
   
   ## Minimal reproduction of the problem with instructions:
   <!--
   If you can illustrate your feature request better with an example, please
   provide the *STEPS TO REPRODUCE* and include the applicable TC version.
   If not, feel free to delete this section.
   -->
   1. Add required capabilities to a delivery service
   2. Add a topology to that delivery service and PUT
   
   <!--
       Licensed to the Apache Software Foundation (ASF) under one
       or more contributor license agreements.  See the NOTICE file
       distributed with this work for additional information
       regarding copyright ownership.  The ASF licenses this file
       to you under the Apache License, Version 2.0 (the
       "License"); you may not use this file except in compliance
       with the License.  You may obtain a copy of the License at
   
       https://apache.org/licenses/LICENSE-2.0
   
       Unless required by applicable law or agreed to in writing,
       software distributed under the License is distributed on an
       "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
       KIND, either express or implied.  See the License for the
       specific language governing permissions and limitations
       under the License.
   -->
   


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



[GitHub] [trafficcontrol] zrhoffman closed issue #5099: Validate topology field on PUT /deliveryservices with respect to required capabilities

Posted by GitBox <gi...@apache.org>.
zrhoffman closed issue #5099:
URL: https://github.com/apache/trafficcontrol/issues/5099


   


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