You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 24, 2025. It is now read-only.
This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:
Traffic Ops
Current behavior:
When making a request to /cdns/dnsseckeys/refresh, a change log entry is created even if there were no DNSSEC keys refreshed:
Refreshed 0 DNSSEC keys
New behavior:
If 0 DNSSEC keys are refreshed via a request to /cdns/dnsseckeys/refresh, a change log entry should not be created. While it's nice to know that the cron job is working, this is mostly useless information. A change log entry is really only necessary if any keys are actually refreshed.
This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:
Current behavior:
When making a request to
/cdns/dnsseckeys/refresh, a change log entry is created even if there were no DNSSEC keys refreshed:New behavior:
If 0 DNSSEC keys are refreshed via a request to
/cdns/dnsseckeys/refresh, a change log entry should not be created. While it's nice to know that the cron job is working, this is mostly useless information. A change log entry is really only necessary if any keys are actually refreshed.