I have two questions concerning content management. I think I understood the concept of the different components like cv or products provided by katello. A cv allows to version current states of repositories and push them through a lifecycle. If I don’t want versioning, I can simply point an activation key to the “Library Environment” and the “Default Organization View”. This leads to having always the latest repository content available on subscriber side.
I got both scenarios working on different clients. Everything fine so far. But now, I would like to achieve a combination of both. Let’s take the example of a GitLab server:
- I don’t want to version the OS Repositories and have always the latest packages available on the clients without having to release new cv versions on every maintenance window.
- For GitLab packages, I want to have versioning in place and test new releases before having them available on production systems.
I created a a graphic to show my idea:
Is this possible? Until now, I haven’t found a solution for this idea. Or do you think it is even a bad idea?
This leads me into my second question. I have a content view - lets say again for the gitlab repository. During the the synchronization a new gitlab-ce package version is downloaded. Does this new package appear as installable update on the content host view or do I have to publish a new cv version to see, that there is a new version available?