Project

General

Profile

Feature #18228

[RFE] Component view versions for composite content views

Added by Pat Riehecky over 5 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Content Views
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

I have a few hundred Composite Content Views that pull primarily from a set of about 10 traditional Content Views.

Eventually, for auditing purposes, I need to know what the version of a traditional Content View was when the Composite Content View was assembled.

Behavior:
  • content_view_rhel7 7.0 can show me what it is in it and where it came from based on the repos included
  • composite_content_view 4.0 can show me what it contains, but not which versions of what views were used

This leaves me having to manually compare the traditional Content Views to the Composite Content View until I find what matches.

Ideally if this could be exposed to the client as a structured fact from the ENC, I can capture it a number of possible ways.

Problem replication workflow:
  • I need to update my_composite_content_view to include a newer version of my_tools_content_view
  • I update my_other_content_view to use a new version, but not my_tools_content_view due to a miss click in the UI
  • I hit publish
  • There isn't a clean way for me to review that the newest version of my_composite_content_view contains the expected version of my_tools_content_view
Example work flow with proposed behavior change:
  • myhost.example.com uses my_composite_content_view 5.0
  • myhost.example.com has an API available method for the name and version of the content view
  • my_composite_content_view 5.0 has an API available interface for seeing
    • when it was created
    • what traditional Content Views were used at creation time of the Composite View
    • the version numbers of each utilized content view used at creation time of the Composite View
    • the creation date of each utilized content view used at creation time of the Composite View

This workflow would allow me to manage Errata for non-updateinfo enabled yum repos as well as track how recently the puppet modules were rebased off our standard puppet module view. At this time I can only say when a view was last published, not if it contains anything current.

Associated revisions

Revision ab643413 (diff)
Added by Pat Riehecky about 5 years ago

Fixes #18228 - Add CV/CCV info to client facts

History

#1 Updated by Justin Sherrill over 5 years ago

  • Legacy Backlogs Release (now unused) set to 114

#2 Updated by The Foreman Bot about 5 years ago

  • Status changed from New to Ready For Testing
  • Legacy Backlogs Release (now unused) deleted (114)
  • Pull request https://github.com/Katello/katello/pull/6792 added

#3 Updated by Justin Sherrill about 5 years ago

  • Legacy Backlogs Release (now unused) set to 250
  • Difficulty set to easy

#4 Updated by Pat Riehecky about 5 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#5 Updated by Ondřej Pražák almost 5 years ago

  • Bugzilla link set to 1343181

#6 Updated by Ondřej Pražák about 4 years ago

  • Bugzilla link changed from 1343181 to 1343180

Also available in: Atom PDF