Release version centos, repository-sets

Support
10

BTW, what I mentioned in the second half of my last response is exactly how I “faked” the functionality. Here is what I did:

  1. Create Product (e.g. CentOS 7)
  2. Add repositories for CentOS 7 (os/updates/extras) from mirror
  3. Add repositories for version locked CentOS 7 (e.g. 7.5.1804) from vault
  4. Sync repositories, create content view, publish to desired lifecycle environment.
  5. Create activation key for CentOS 7, add subscription for product. In repository sets, disable 7.5 repos.
  6. Create key for CentOS 7.5, add subscription for same product. In repository sets, disable 7 repos.

After this, you should have one product and one content view hosting repos for multiple versions. You will have one key for each version. Technically all the repos will be exposed to the clients, but will be disabled by default. If you really didn’t want the repos exposed at all, then you could still use a single product, but would need different content views and only add the repositories for each version, then use separate keys for each CV.

The real downside of this way is having such a large content view to publish, promote, and sync with smart proxies. Also slightly further complicating this particular example is adding CEFS functionality so that I have proper errata. Out of scope for my example but it’s just a bit more work. Well worth it for CentOS deployments though.