Adding a new repo as 'enabled' by default

[chatlow]

Quick question; I understand that majority of users preferred to have newly added repos in Foreman added to a machine but left in disabled state. I personally don’t have a use-case for this and would much rather they get enabled immediately as it’s always something we forget to do and catches us out when upgrading

Anyway, is there a way to enable these by default when added?

thanks

[jeremylenz]

There is no way to change the default enablement state of custom repos.

If you are adding a new custom repo and want it to be available to new hosts, add a content override (“Repository sets” - Override to enabled) in the activation key.

If you want it to be available to existing hosts, add the content override via a host bulk action. In the latest Katello, bulk Repository Sets actions are available in the new UI. Or you can also use the old content hosts UI.

The default enablement was changed a while back to make it easier in an SCA-only world. You can read all of that discussion here –> [RFC] Making things easier when working with custom products & Simple Content Access (SCA)

and

Katello 4.9 Custom products changes with SCA

Now that Katello 4.9RC1 is out, I’m interested to see how upgrading goes from Katello 4.8. On a Katello 4.9, custom products should be disabled by default, and you’ll have “enabled” overrides for all existing hosts and activation keys. For an overview of the feature, see https://github.com/Katello/katello/pull/10502. To read the looooong discussion with context, see [RFC] Making things easier when working with custom products & Simple Content Access (SCA) The task that creates these runs dur…