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/07/15 20:08:07 UTC
[GitHub] [trafficcontrol] mitchell852 edited a comment on issue #3723: DS
creation - behaviour should be consistent when an associated field is
deleted before DSR fulfillment
mitchell852 edited a comment on issue #3723: DS creation - behaviour should be consistent when an associated field is deleted before DSR fulfillment
URL: https://github.com/apache/trafficcontrol/issues/3723#issuecomment-511549351
For scenario 1 these are the delivery service types:
![image](https://user-images.githubusercontent.com/251272/61245220-3c510e00-a709-11e9-8ed5-89d61f5914b3.png)
and although TP and the TO api allows you to create new delivery service types, you really shouldn't because without other code changes, your new "type" will have no effect. These types are static in nature. Can you check in dev console to ensure that an error isn't being returned and maybe the UI is simply failing to display it?
^^ really, an issue here (in addition to the missing error message) is that TP/TO API should not let you create "static" types. On the other hand, creating "dynamic" types is OK. i.e. EDGE_FOO or MID_FOO i think are the only 2 types that you can create dynamically.
----------------------------------------------------------------
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