<!-- ************ STOP!! ************ If this issue identifies a security vulnerability, DO NOT submit it! Instead, contact the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the guidelines at https://apache.org/security regarding vulnerability disclosure. - For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/slack-invite) or the Traffic Control Users mailing list (send an email to users-subscribe@trafficcontrol.apache.org to subscribe). - Before submitting, please **SEARCH GITHUB** for a similar issue or PR * https://github.com/apache/trafficcontrol/issues * https://github.com/apache/trafficcontrol/pulls --> <!-- Do not submit security vulnerabilities or support requests here - see above --> ## This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components: <!-- delete all those that don't apply --> - Traffic Ops ## Current behavior: <!-- Describe how the current features are insufficient. --> The Traffic Ops DNSSEC refresh cron job still uses the Perl implementation: https://github.com/apache/trafficcontrol/blob/a971b6c50b6a429ddbbbdfd2ca8ff1107b659eb8/traffic_ops/etc/cron.d/trafops_dnssec_refresh#L18 ## New behavior: <!-- Describe how this change would improve Traffic Control --> The cron job should use the Go implementation ([`/traffic_ops/app/bin/checks/DnssecRefresh/ToDnssecRefresh.go`](https://github.com/apache/trafficcontrol/blob/a971b6c50b/traffic_ops/app/bin/checks/DnssecRefresh/ToDnssecRefresh.go)).
This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:
Current behavior:
The Traffic Ops DNSSEC refresh cron job still uses the Perl implementation:
trafficcontrol/traffic_ops/etc/cron.d/trafops_dnssec_refresh
Line 18 in a971b6c
New behavior:
The cron job should use the Go implementation (
/traffic_ops/app/bin/checks/DnssecRefresh/ToDnssecRefresh.go).