The Debian plugin uses that to configure repository metadata signing. It is handy to not have to define it on a per-repo basis.
I can also see how it might be useful for the Docker plugin, which (I believe) allows you to redirect the actual downloading of the layers to a different system. Again, it would be helpful if the distributor wouldn't have to be individually configured. On Thu, Oct 5, 2017 at 1:26 PM, Chadwick Banning <[email protected]> wrote: > I'd like to see https://pulp.plan.io/issues/1251 implemented. > > On Thu, Oct 5, 2017 at 11:13 AM, Michael Hrivnak <[email protected]> > wrote: > >> As part of Pulp 3 planning, we could use your insights about which global >> importer settings you use with Pulp 2. Your feedback will influence what we >> implement for Pulp 3. >> >> To re-cap, you can use files in /etc/pulp/server/plugins.conf.d/ to >> declare global settings for your importers. The most common use case is to >> configure a proxy in one place. >> >> Do you use this feature? If so, do you use it for any other configuration >> items besides the proxy? >> >> Getting more specific, if Pulp 3 only allowed you to manage proxies >> globally, and all other importer settings had to be managed at the >> per-importer level, would that work for you? >> >> Thanks! >> >> -- >> >> Michael Hrivnak >> >> Principal Software Engineer, RHCE >> >> Red Hat >> >> _______________________________________________ >> Pulp-list mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/pulp-list >> > > > > -- > Chadwick Banning > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
