Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
2.1.0
-
None
-
None
-
Few variables in the TRAFFIC_ROUTER default profile published at http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops uses the pattern ${toHostname}, however, at least till commit 3980b41797c8f2b616277df4b74e73a011c48869, traffic router does not replace this pattern with the ops hostname.
I would suggest to add a "README" besides the default profile, with instructions to replace this pattern manually (until TR supports it)Few variables in the TRAFFIC_ROUTER default profile published at http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops uses the pattern ${toHostname}, however, at least till commit 3980b41797c8f2b616277df4b74e73a011c48869, traffic router does not replace this pattern with the ops hostname. I would suggest to add a "README" besides the default profile, with instructions to replace this pattern manually (until TR supports it)
Description
Few variables in the TRAFFIC_ROUTER default profile published at http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops uses the pattern ${toHostname}, however, at least till commit 3980b41797c8f2b616277df4b74e73a011c48869, traffic router does not replace this pattern with the ops hostname.
I would suggest to add a "README" besides the default profile, with instructions to replace this pattern manually (until TR supports it)