Bug 1745726 - [RFE] - Add ability to include facts on list of consumers
Summary: [RFE] - Add ability to include facts on list of consumers
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 2.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: candlepin-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-26 18:22 UTC by Tramaine Darby
Modified: 2022-02-14 15:07 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-02-14 15:07:50 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1647724 0 medium CLOSED GET /consumers does not include consumer facts 2024-02-02 13:10:47 UTC

Description Tramaine Darby 2019-08-26 18:22:43 UTC
Description of problem: In the OpenShift Cluster Manager application - there is logic to cleanup consumers (delete consumers for which the clusters have been deleted or archived). we have the cluster ID as a fact in the consumer in order to be able to make the relation. so I take the list of consumers belonging to an org, and use the cluster ID in facts to compare which ones still exist. however, since the list doesn't include facts, I have to query each consumer we got just in order to have the facts and be able to compare. it's an important bottleneck in the job today.

this is the exact place: https://gitlab.cee.redhat.com/service/uhc-account-manager/blob/develop/pkg/services/reconcile/reconcile_organization.go#L65

note that's listing consumers for an owner, in /owners/ID/consumers

Desired change: Add an ?includeFacts=true flag on the call to /owners/ID/consumers to return the facts on each consumer returned in the list.

Comment 2 Tramaine Darby 2022-02-14 14:38:34 UTC
We believe this use case is no longer an issue, and do not need this change.

Comment 3 Nikos Moumoulidis 2022-02-14 15:07:50 UTC
Closing as per comment #2


Note You need to log in before you can comment on or make changes to this bug.