Bug 1444156

Summary: [RFE] Custom product repositories should be disabled by default to content host
Product: Red Hat Satellite Reporter: Rajan Gupta <rajgupta>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.8CC: arusso, bbuckingham, bkearney, cdonnell, christoph.roeder, csulekha, jalviso, jcallaha, lochrini, pghadge, vgunasek, vijsingh
Target Milestone: UnspecifiedKeywords: FutureFeature, PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-21 01:54:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 2 Ian 2017-09-07 22:07:21 UTC 
In addition to being enabled on all hosts it also gets enabled in all the activation keys which should also, optionally, be disabled.
Comment 3 Chandni Sulekha 2018-01-31 07:20:35 UTC 
Description of RFE:

Customer would like to have the Custom product repositories should be disabled by default so that repository should not available to all the content host by default.


When adding a new repository to a content view and then publishing that content view to an environment, all hosts in that environment will automatically see the new repository and enable it.

Is it possible to prevent a new repository from being auto-enabled?

For eg.
The repository is an internal one labeled 'transient-ansible' inside of content view 'cv-transient-repos' which is part of composite content view 'Infrastructure Systems' that is associated with some hosts
Comment 5 jalviso 2018-05-21 01:54:58 UTC 

*** This bug has been marked as a duplicate of bug 1265120 ***