Bug 1706382

Summary: Group subcommand should support listing IDs
Product: Red Hat Enterprise Linux 8 Reporter: Michal Domonkos <mdomonko>
Component: dnfAssignee: Jaroslav Mracek <jmracek>
Status: CLOSED ERRATA QA Contact: Eva Mrakova <emrakova>
Severity: unspecified Docs Contact:
Priority: low    
Version: 8.0CC: amatej, james.antill, tbowling
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: dnf-4.2.16-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:47:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michal Domonkos 2019-05-04 14:25:39 UTC
Currently, in order to list group IDs, DNF must be run in verbose mode.  Since using group IDs is arguably much more comfortable than having to always spell out the whole group names whenever operating on groups, forcing users to enable verbose mode to obtain the IDs seems plain wrong (and is a regression against YUM3 which knew the "ids" argument).

That said, we should probably add a new option called "--ids" (with the "ids" fallback for YUM3 compatibility).

Related docs bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1701859

Comment 2 Jaroslav Mracek 2019-10-25 11:57:29 UTC
I create a patch (https://github.com/rpm-software-management/dnf/pull/1513) that implements --ids.

Comment 3 Jaroslav Mracek 2019-10-25 12:23:55 UTC
Tests are available here: https://github.com/rpm-software-management/ci-dnf-stack/pull/665

Comment 9 errata-xmlrpc 2020-04-28 16:47:49 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1823