Req: streamline errata updates #777
Description
If errata updates are requested using "patchman -e" all architectures seem to be pulled regardless of whether there are actually any hosts of that architecture type present in the database.
Seems wasteful of traffic and especially time, however, if a host is subsequently introduced.. tadaa... the errata updates are already present, so yeah.
Could there be scope for an optional admin setting, tickbox to skip erratas with zero hosts that the end user can tick or untick as they wish. So an architecture isnt pulled unnecessarily? Does the data stored on hosts allow for this kind of logic?
May speed up processing on server if not may architectures in use.
(I realise this isnt appropriate to CVE data due to the way CVEs are categorised, we wouldnt want to pull data just to discard it so the above limited to erratas).
Close if not appropriate, thank you for patchman!