On Thu, Nov 10, 2016 at 12:24 PM, 'Jason B. Nance' via Foreman users < [email protected]> wrote:
> Hi Tom, > > I don't believe that download policy is an attribute of a content view, > only of a product repository, as packages aren't really owned by CVs, they > are just referenced by CVs. So this change would really be at the > product/repo level and affect consumers of that repo. You should be able > to change the download policy of a repository at any time regardless of > whether it is referenced via a CV or not and then initiate a sync (such as > if you are moving from on demand to immediate). > > Sorry if I'm not following you, > > j > > Each version of a content view has a reference to its own version of a product repo. So for CV-1.0, there is a repo, and for CV-2.0 there is a repo. My goal would be to allow the attributes of these separate repos to be managed separately. How that management is presented to user user (eg. is it tied to the content view, the lifecycle environment, or that version of a repo) would be worth discussing. I'm interested, though, if anyone else has seen the need for something like this. > > ------------------------------ > *From: *"Tom McKay" <[email protected]> > *To: *[email protected] > *Sent: *Thursday, November 10, 2016 10:20:53 AM > *Subject: *[foreman-users] [katello] modifying repository attributes in > content views > > There are times when I wish I could edit the attributes of a repository in > a specific content view and am wondering how hard this would be. > > For example, I sync RHEL-7.2 with a download policy of on demand. From > there I craft a content view with specific filters and publish and promote > it to my production lifecycle environment. At that point, I'd like to use > inter-server sync (ISS) to export for use in another organization. However, > ISS does not work with on demand. For my use case, I'd like to switch the > download policy of the specific repo in the product content view to > immediate, then sync it to pull down all the packages. > > Another use case would be creating unprotected custom product repos > ("Publish via HTTP") but then when they make it to my production > environment, switching them to protected HTTPS. > > Is manipulating aspects of repositories in content views something others > would find useful? Is this a difficult thing to implement? > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
