On Thu, Nov 10, 2016 at 12:24 PM, 'Jason B. Nance' via Foreman users < [ mailto:[email protected] | [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. In your example of download policies how would this work, though? Each CV doesn't have its own copy of a package, right? I thought that CVs were basically just symlinks and database entries and that pulp was unaware of them. I don't mean to derail and I'm sorry if I'm focusing too much on one specific example. You noted download policy and http/https publishing. Is that where you would draw the line or would you also include mirror on sync, metadata, etc? j -- 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.
