Project

General

Profile

Bug #11298

hammer content-view info should list the associated project for repositories

Added by Greg Swift almost 4 years ago. Updated 12 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
Hammer
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

When creating repositories we don't prefix the repository name with the name of the product (cause redundant). And when you view the repositories via the cli, that fine. Viewing the content views in the ui is fine as well.

hammer> repository list --organization-id 1 --by id
---|---------------------|----------------|--------------|--------------------------------------------------------------------------
ID | NAME                | PRODUCT        | CONTENT TYPE | URL                                                                      
---|---------------------|----------------|--------------|--------------------------------------------------------------------------
16 | el7-64-updates      | CentOS         | yum          | http://mirror.rackspace.com/centos/7/updates/x86_64/                     
3  | el7-64-products     | Puppet         | yum          | http://yum.puppetlabs.com/el/7Server/products/x86_64/                    
13 | el7-64-os           | CentOS         | yum          | http://mirror.rackspace.com/centos/7/os/x86_64/                          
15 | el7-64-fasttrack    | CentOS         | yum          | http://mirror.rackspace.com/centos/7/fasttrack/x86_64/                   
14 | el7-64-extras       | CentOS         | yum          | http://mirror.rackspace.com/centos/7/extras/x86_64/                      
4  | el7-64-dependencies | Puppet         | yum          | http://yum.puppetlabs.com/el/7Server/dependencies/x86_64/                
18 | el7-64              | EPEL           | yum          | http://mirror.rackspace.com/epel/7/x86_64/                               
12 | el6-64-updates      | CentOS         | yum          | http://mirror.rackspace.com/centos/6/updates/x86_64/                     
2  | el6-64-products     | Puppet         | yum          | http://yum.puppetlabs.com/el/6Server/products/x86_64/                    
9  | el6-64-os           | CentOS         | yum          | http://mirror.rackspace.com/centos/6/os/x86_64/                          
11 | el6-64-fasttrack    | CentOS         | yum          | http://mirror.rackspace.com/centos/6/fasttrack/x86_64/                   
10 | el6-64-extras       | CentOS         | yum          | http://mirror.rackspace.com/centos/6/extras/x86_64/                      
1  | el6-64-dependencies | Puppet         | yum          | http://yum.puppetlabs.com/el/6Server/dependencies/x86_64/                
21 | el6-64              | Puppet         | yum          | http://yum.puppetlabs.com/el/6Server/products/x86_64/                    
17 | el6-64              | EPEL           | yum          | http://mirror.rackspace.com/epel/6/x86_64/                               
---|---------------------|----------------|--------------|--------------------------------------------------------------------------

I added id #21 (Puppet el6-64) just so there would be a duplicate repo name for display purposes

However when I view the content-view via the cli its hard to tell what repo comes from what product.

hammer> content-view info --organization-id 1 --id 2
ID:                     2
Name:                   Weekly Core
Label:                  weekly-core
Composite:              false
Description:            
Content Host Count:     0
Organization:           Default Organization
Yum Repositories:       
 1) ID:    9
    Name:  el6-64-os
    Label: el6-64-os
 2) ID:    12
    Name:  el6-64-updates
    Label: el6-64-updates
 3) ID:    3
    Name:  el7-64-products
    Label: el7-64-products
 4) ID:    4
    Name:  el7-64-dependencies
    Label: el7-64-dependencies
 5) ID:    17
    Name:  el6-64
    Label: el6-64
 6) ID:    15
    Name:  el7-64-fasttrack
    Label: el7-64-fasttrack
 7) ID:    13
    Name:  el7-64-os
    Label: el7-64-os
 8) ID:    16
    Name:  el7-64-updates
    Label: el7-64-updates
 9) ID:    18
    Name:  el7-64
    Label: el7-64
 10)ID:    10
    Name:  el6-64-extras
    Label: el6-64-extras
 11)ID:    14
    Name:  el7-64-extras
    Label: el7-64-extras
 12)ID:    1
    Name:  el6-64-dependencies
    Label: el6-64-dependencies
 13)ID:    11
    Name:  el6-64-fasttrack
    Label: el6-64-fasttrack
 14)ID:    2
    Name:  el6-64-products
    Label: el6-64-products
Docker Repositories:    

Puppet Modules:         

Lifecycle Environments: 

Versions:               

Components:             

Activation Keys:

History

#1 Updated by Greg Swift almost 4 years ago

after posting that and looking at it again... i'm not sure why the same view isn't just used everywhere?

#2 Updated by Eric Helms almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 70
  • Triaged changed from No to Yes

#3 Updated by Justin Sherrill over 3 years ago

  • Legacy Backlogs Release (now unused) changed from 70 to 86

#4 Updated by Eric Helms about 3 years ago

  • Assignee set to Adam Price
  • Legacy Backlogs Release (now unused) changed from 86 to 144

#5 Updated by Eric Helms about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 144 to 168

#6 Updated by Eric Helms about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 168 to 114

#7 Updated by Greg Swift almost 3 years ago

Side note... the Katello UI needs to be updated to support this as well. There are several places where you are given a drop down that just contains the repository names all jumbled together.

Also available in: Atom PDF