Project

General

Profile

Actions

Feature #30223

open

Lifecyle based composite content views

Added by Gerald Vogt almost 4 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Content Views
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Currently, composite content views are version based. They pick up the latest version or the version pinned from the component content views. The composite content view has its own completely independent lifecycle from the components.

That makes it difficult to use composite content views if you want to split up application based content views and their own independent lifecycle.

Let's say you have a Base operating system content view and two application content views app1 and app2. For each view there are different people responsible which test pending updates and promote them to testing or production. Thus, if some updates for the base go into production it doesn't mean anything about updates pending for an app.

A lifecycle composite content view would pick up versions from the components based on the environment of the components.

A CCV of those three CVs base, app1, app2 would automatically publish and promote a new version if any of the components gets a promotion.

The lifecycle testing CCV would contain all component versions promoted to the testing environment.
The lifecycle production CCV would contain all component versions promoted to the production environment.
The lifecycle library CCV would be contain the latest versions of the component versions in the library environment.

Whenever a component gets promoted the corresponding lifecycle CCV would publish a new version and promote it to the new environment.

Thus the CCV in the production environment would only contain production environment component CVs. This allows updates for some CVs pushed faster than for others allowing teams responsible for CVs to work independently.

In an extension of this feature it might be possible to select the life cycle environment of each component in a CCV (instead of using the same for all components). Thus, an app1 could be combined with a base cv which is always in production environment.

Actions #1

Updated by Ian Ballou over 3 years ago

  • Target version set to Katello Backlog
  • Triaged changed from No to Yes
Actions

Also available in: Atom PDF