This PR creates symlinks from /opt/<component>/var/log to /var/log/<component> for the log directories that were moved in #7979. This is useful if you have any code or configuration still referencing /opt/<component>/var/log, because it buys some time to change those references to /var/log/<component>, rather than requiring that everything is changed all at once, whenever you deploy #7979.
Because this is intended as a temporary measure, these symlinks are deprecated with the intent of removing them in ATC 9.0.0, assuming there is a release before then that does include the symlinks.
## Which Traffic Control components are affected by this PR?
Traffic Monitor
Traffic Router
Traffic Stats
What is the best way to verify this PR?
Build and install the RPMs, verify the symlinks exist.
cd infrastructure/cdn-in-a-box
make traffic_monitor/traffic_monitor.rpm traffic_router/traffic_router.rpm traffic_router/tomcat.rpm traffic_stats/traffic_stats.rpm
docker-compose build trafficmonitor trafficrouter trafficstats
docker-compose run --rm --no-deps --entrypoint= trafficmonitor ls -l /opt/traffic_monitor/var
docker-compose run --rm --no-deps trafficrouter ls -l /opt/traffic_router/var
docker-compose run --rm --no-deps --entrypoint= trafficstats ls -l /opt/traffic_stats/var
This PR creates symlinks from
/opt/<component>/var/logto/var/log/<component>for the log directories that were moved in #7979. This is useful if you have any code or configuration still referencing/opt/<component>/var/log, because it buys some time to change those references to/var/log/<component>, rather than requiring that everything is changed all at once, whenever you deploy #7979.Because this is intended as a temporary measure, these symlinks are deprecated with the intent of removing them in ATC 9.0.0, assuming there is a release before then that does include the symlinks.
## Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Build and install the RPMs, verify the symlinks exist.
PR submission checklist