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
Currently for each update we get a list of repositories. From these we can use /repos to infer the product name. However, this limits our knowledge of affected products to only those from which we collected package list from.
It would be great if vmaas could aggregate the products for an erratum so that a general list of products a given erratum is applicable to can be requested. (e.g. on errata/erratum_name)
For example:
affected_products: ['Red Hat Enterprise Linux Server 7 x86_64', 'Red Hat Enterprise Linux Server - AUS 7.4 x86_64', ...]
The text was updated successfully, but these errors were encountered:
@MichaelMraka
by "products a given erratum is applicable to" I mean all products an erratum applies to, e.g:
Red Hat Enterprise Linux Server 6
Red Hat Enterprise Linux Workstation 6
Red Hat Enterprise Linux for IBM z Systems 6
etc.
by "products which we collected package list" I mean packages from customer's systems that are checking into Insights. This can be a strict subset of the former i.e. only "Red Hat Enterprise Linux Server 6" servers are checking in to Insights yet we may still want to tell the customer that the erratum is applicable to all those different products (static information)
Currently for each update we get a list of repositories. From these we can use
/repos
to infer the product name. However, this limits our knowledge of affected products to only those from which we collected package list from.It would be great if vmaas could aggregate the products for an erratum so that a general list of products a given erratum is applicable to can be requested. (e.g. on
errata/erratum_name
)For example:
The text was updated successfully, but these errors were encountered: