Vijay-1 commented on issue #2029: [Issue 1907] TO API for backup edge cachegroup URL: https://github.com/apache/incubator-trafficcontrol/pull/2029#issuecomment-381702372 @mitchell852 PUT was there in the original proposal but it was removed based on one of your comments. I think, you want PUT to update which means alter an existing list instead of deleting an entire list and inserting which was PUTs original behaviour we had earlier. Am i right? If yes, i believe the original proposal should work fine instead of altering the list. Given below is the original proposal: 1. POST: receive a full list of ordered backups and create the fallback list. If the fallback list already exists, render a failure. 2. PUT: receive a full list of ordered backups, delete the existing fallback list, and create a new fallback list. If the fallback list does not exist yet, render a failure. 3. DELETE: delete the existing fallback list for a cachegroup. If the fallback list does not exist, render a failure. 4. GET: return the existing fallback list for a cachegroup. If the fallback list does not exist, render a failure. Also i am not sure why we need Get all cachegroup fallbacks. I dont see any point in pulling all the cachegroup fallbacks instead it makes sense that we always retrieve fallbacks with respect to a cache group. Also I am not sure on why we need to delete a specific fallback if there is an update (PUT) available
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
