mitchell852 commented on issue #2029: [Issue 1907] TO API for backup edge 
cachegroup
URL: 
https://github.com/apache/incubator-trafficcontrol/pull/2029#issuecomment-382010522
 
 
   @Vijay-1 
   
   The Traffic Portal typically works like this. Here are a few scenarios:
   
   1. you retrieve a list of something. in this case, probably a list of 
fallbacks for a cachegroup.
   2. you can click on a fallback in the list to edit it 
   
   or 
   
   1. you retrieve a list of something
   2. you can click on something in the list to delete it
   
   or 
   
   1. you retrieve a list of something
   2. you can add a new thing to the list
   
   so basically if you want to integrate your apis into the TP, you need 
endpoints to do the following:
   
   1. fetch a list of fallbacks for a cachegroup or cachegroups for a fallback 
(GET /cachegroup_fallbacks[?cachegroupId=|?fallbackId=])
   2. fetch one cg fallback (GET 
/cachegroup_fallbacks[?cachegroupId=4&fallbackId=6]) <-- since you have  no ID 
field, maybe you use both to identify a row to fetch
   3. update one cg fallback (PUT 
/cachegroup_fallbacks[?cachegroupId=4&fallbackId=6]) <-- since you have  no ID 
field, maybe you use both to identify a row to update
   4. delete one fallback (DELETE 
/cachegroup_fallbacks[?cachegroupId=4&fallbackId=6]) <-- since you have  no ID 
field, maybe you use both to identify a row to delete
   5. create one or more fallbacks (POST /cachegroup_fallbacks [ { 
"cacheGroupId": 1, "fallbackId": 27, "fallbackOrder": 10 }, {...} ]) <-- this 
just adds to the list. it doesn't wipe it out first.
   
   without these routes, you are going to have a hard time integrating these 
apis into the traffic portal. actually, you could probably do without #2 and #3 
and just go with:
   
   1. fetch list
   2. delete one
   3. create one (or more) <-- no deleting thought. just add to the existing 
list
   
   
   
   
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to