Bug 735434 - pulp-admin repo list and info should show repo url
Summary: pulp-admin repo list and info should show repo url
Alias: None
Product: Katello
Classification: Retired
Component: Client
Version: 1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Bryan Kearney
QA Contact: Katello QA List
Depends On:
TreeView+ depends on / blocked
Reported: 2011-09-02 15:45 UTC by Mike McCune
Modified: 2011-09-02 15:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-09-02 15:46:40 UTC

Attachments (Terms of Use)

Description Mike McCune 2011-09-02 15:45:59 UTC
There is no way as a user to know the path to the repo on the pulp service itself after you create it.  You have to just know that they are found at:


the command 'distribution list' shows the URL to the tree:

$ pulp-admin distribution list
       List of Available Distributions

Id                    	ks-kstree-noarch         
Description           	ks-kstree-noarch          
URL                   	https://localhost/pulp/ks/repo/f15-x86_64/

we should do the same for repos:

$ pulp-admin repo list
       List of Available Repositories

Id                 	kstree                   
Name               	kstree                   
Feed URL  
Feed Type          	remote                   
Content Type       	yum                      
Feed Certs         	CA:No   Cert:No
Consumer Certs     	CA:No   Cert:No
Architecture       	noarch                   
Sync Schedule      	None                     
Packages           	2935                     
Files              	0                        
Distributions      	ks-kstree-noarch         
Publish            	True                     
Clones             	[]                       
Groups             	None                     
Filters            	[]                       
Notes              	{}                       
URL                     https://localhost/pulp/repo/f15-x86_64/

Comment 1 Mike McCune 2011-09-02 15:46:40 UTC
oops, wrong product

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