Bug 783406 - Better formatting for package_group info
Summary: Better formatting for package_group info
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Katello
Classification: Retired
Component: Client
Version: 1.X
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Tomas Strachota
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-20 10:25 UTC by Tomas Strachota
Modified: 2012-07-17 13:09 UTC (History)
1 user (show)

Fixed In Version: katello-cli-0.2.7-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-17 13:09:40 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tomas Strachota 2012-01-20 10:25:03 UTC 
Description of problem:
CLI command 'package_group info' doesn't format all it's output properly.

  
Actual results:
Id:                        birds
Name:                      birds
Description:               
Mandatory Package Names:   [u'stork', u'cockateel', u'penguin', u'duck']
Default Package Names:     []
Optional Package Names:    []
Conditional Package Names: {}

Expected results:
Better formatting, not only printed python lists and hashes.
Comment 1 Sachin Ghai 2012-05-15 06:45:27 UTC 
Verified with following katello build:

katello-cli-0.2.33-1.el6.noarch
katello-0.2.35-1.el6.noarch

Now formatting looks good. 

--
katello> package_group info --repo_id 775 --id birds
--------------------------------------------------------------------------------
                          Package Group Information
--------------------------------------------------------------------------------

Id:                        birds
Name:                      birds
Description:
    None
Mandatory Package Names:
    stork
    cockateel
    penguin
    duck
Default Package Names:
    None
Optional Package Names:
    None
Conditional Package Names:
    None

--
Comment 2 Bryan Kearney 2012-07-17 13:09:40 UTC 
Moving all community bugs with fixes to closed.
Note You need to log in before you can comment on or make changes to this bug.