Re: [Pulp-dev] file repository type

Forgot to reply-all as usual. On Jun 6, 2017 5:10 PM, wrote: I thought I had an RFE in for this a couple years ago. It would be very nice to do non-manifest syncs against non-pulp remote sources. Especially if it supported the concept of recursive folder/file syncs. On Jun 6, 2017 4:47 PM,

Re: [Pulp-dev] file repository type

The key is in discovery of files. There's no standard we know of that would be helpful, which is why we depend on a PULP_MANIFEST to tell us what files are available. Maybe there are some cases when a particular service has a well-defined way of expressing what files are available, in which case

Re: [Pulp-dev] PUP-3: Proposal to change our git workflow

Looks like @bmbouter made a comment to include this but I forgot to include it: https://github.com/pulp/pups/pull/3#discussion_r111498031 Will update the PUP. David On Tue, Jun 6, 2017 at 3:48 PM, Michael Hrivnak wrote: > > On Tue, Jun 6, 2017 at 9:58 AM, Brian Bouterse

Re: [Pulp-dev] file repository type

You do not need to create a manifest in order to upload. You only need one in order to sync. Here is documentation about upload: http://docs.pulpproject.org/plugins/pulp_rpm/user-guide/isos.html#uploading-isos-to-a-repository You can also create the manifest file in 3-4 lines of bash. Maybe it

Re: [Pulp-dev] [pulp 3] cast() method for casting from a Master to Detail model instance

> > > I think there is still an improvement to be made with cast() when it fails > to cast. The cast method itself can't know if you're dealing with the > master or most detailed object, but the code author calling cast() always > knows and if they don't need it cast() they shouldn't call cast().