rawlinp commented on a change in pull request #4537: Add blueprint for Flexible Topologies URL: https://github.com/apache/trafficcontrol/pull/4537#discussion_r408927933
########## File path: blueprints/flexible-topologies.md ########## @@ -250,11 +250,29 @@ response JSON: ##### `/deliveryservices` endpoints -All relevant Delivery Service APIs will have their JSON request and response objects modified to include a new `topology` field which references the name of the topology it's assigned to: -```JSON +All relevant Delivery Service APIs will have their JSON request and response objects modified to include the following new fields: +- `topology` - the name of the topology it's assigned to +- `firstHeaderRewrite` - the header_rewrite ATS config that will be applied to the *first tier* caches in the Delivery Service's Topology +- `middleHeaderRewrite` - the header_rewrite ATS config that will be applied to all *middle tier* caches in this Delivery Service's Topology +- `lastHeaderRewrite` - the header_rewrite ATS config that will be applied to all *last tier* caches in this Delivery Service's Topology Review comment: Yeah, I was considering `intermediateHeaderRewrite`/`innerHeaderRewrite` vs `middleHeaderRewrite` because it is close like you said. Honestly I would like to continue using `edgeHeaderRewrite` too since that still makes sense in the topology world, but I'm not sure we can take those fields as-is without some manual migration to the new fields. `root` can be confusing because origins are really the "root", but they don't have to be in the topology. Plus a topology isn't truly a tree, so there isn't really a root either. ---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
