Bug 589185

Summary:	a repo's metadata (or its associated content sources' metadata) should include which ResourceTypes its packages apply to
Product:	[Other] RHQ Project	Reporter:	Ian Springer <ian.springer>
Component:	Content	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED WONTFIX	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.3.1	CC:	ccrouch, jshaughn
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-29 17:40:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ian Springer 2010-05-05 15:31:32 UTC

For example the JBoss Patches (i.e. CSP) repo would specify that its packages apply to the JBossAS Server (JBossAS) and JBoss Server (JBossAS5) ResourceTypes.

That way, when a user goes to the Content>Subscriptions for a JBoss AS Server Resource, they would see the JBoss Patches repo listed as a repo to which that Resource can subscribe, but when they go to some other type of Resource (e.g. a Postgres Server, a Datasource, or an EAR), they would not see the JBoss Patches repo listed.

Comment 1 Joseph Marques 2010-09-16 16:57:49 UTC

ian, i thought this kind of metadata was already supported in the rss feed to the CSP.  is this an issue of more recent patches not including this data, but the older patches do?  in short, do we need to do any work here, or is this an oversight during feed generation that our plugin consumes?