[GitHub] [trafficcontrol] srijeet0406 commented on pull request #5974: Every endpoint that modifies a CDN, or components related to a CDN, needs to be "lock safe"

[GitBox <gi...@apache.org>]

srijeet0406 commented on pull request #5974:
URL: https://github.com/apache/trafficcontrol/pull/5974#issuecomment-875847845


   > Do you have a list anywhere of the endpoints this affects? The blueprint didn't include one iirc because it was just a bit too pedantic for a blueprint, but I think it'd be nice to know which endpoints are "lock-able" - would also maybe help reviewers verify that everything that _should_ be locked _is_.
   
   Yeah, you're right. I didn't include a list of endpoints in the blueprint, but I'll list them out here:
   
   POST/ PUT/ DELETE endpoints for the following:
   CDNs (not Post, because the CDN needs to be present for a user to be able to lock it)
   Servers
   Cachegroups (while assigning and unassigning servers)
   Cachegroup parameters
   Topologies (while adding or deleting cachegroups)
   DeliveryServices
   Delivery Service related cert or key renewal/ creation/ deletion
   Delivery Service Servers
   Delivery Service Regexes
   Federations
   Origins
   Profiles
   Profile Parameters
   
   
   


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

To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org