[Pulp-dev] file repository type
bbouters at redhat.com
Tue Jun 6 20:46:24 UTC 2017
What if the pulp_file plugin (the pulp3 one) would support syncing files
directly from remotes without a manifest? Like syncing from a remote
webserver or version control system. Maybe that would be a VCS plugin, not
the file_plugin, but regardless, other software similar to Pulp supports
 that use case.
On Mon, Jun 5, 2017 at 1:10 PM, Michael Hrivnak <mhrivnak at redhat.com> wrote:
> 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:
> You can also create the manifest file in 3-4 lines of bash. Maybe it would
> be useful for Pulp to include a small script that can generate the manifest.
> That said, you can always upload your files to a Pulp repo, and publish
> it, which will cause Pulp to create a new manifest for you.
> On Mon, Jun 5, 2017 at 6:41 AM, Tom McKay <thomasmckay at redhat.com> wrote:
>> I'd like to sync individual files and folders (recursively?) into pulp
>> via foreman. Apparently, though, I need to create a pulp manifest in order
>> to upload. Is this necessary or can pulp do it for me? Or should I build
>> this into foreman? @ehelms provided a gist of the steps and it seems
>> pretty basic and something pulp could be doing itself.
>> My use case is that I wanted to import a build file for openshift from
>> github, then promote that file (and other artifacts) through foreman's life
>> cycle environments. A lot of demos and tutorials for openshift start from
>> git and other non-local components.
>>  https://gist.github.com/ehelms/3fd956ee887db3d7bac20b29efa3dd51
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
> Michael Hrivnak
> Principal Software Engineer, RHCE
> Red Hat
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev