The ct-fetch job now saves metadata in redis about which log entries it has seen. With this PR, aggregate-known will read the CT log metadata from redis and save it in a "ct-logs.json" file. It's important that aggregate-known performs this task, and not moz_kinto_publisher, because ct-fetch runs continuously and we want the metadata at the time when aggregate-known was called.
The
ct-fetchjob now saves metadata in redis about which log entries it has seen. With this PR,aggregate-knownwill read the CT log metadata from redis and save it in a "ct-logs.json" file. It's important thataggregate-knownperforms this task, and notmoz_kinto_publisher, because ct-fetch runs continuously and we want the metadata at the time whenaggregate-knownwas called.Resolves #194