one-shot approach sounds good to me.
+1
Regards,
Ina Panova
Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there is no path and leave a trail."
On Thu, Apr 11, 2019 at 6:05 PM Daniel Alley wrote:
> The one-shot approach basically means
The one-shot approach basically means that every plugin will need to
implement this separately from boilerplate code. Therefore, I suppose the
best course of action is to write a story to implement this for Pulp RPM,
implement it there, and copy said boilerplate to the plugin template.
Any
On Sat, Apr 6, 2019 at 11:48 AM Justin Sherrill wrote:
>
> On 4/4/19 2:35 PM, Daniel Alley wrote:
>
> Content copy between repositories is critically important to Katello
> integration and is something that we have not really addressed yet. It
> also needs to be completed before the RPM plugin
On 4/4/19 2:35 PM, Daniel Alley wrote:
Content copy between repositories is critically important to Katello
integration and is something that we have not really addressed yet.
It also needs to be completed before the RPM plugin can begin work on
depsolving. The story that results from this
I think its possible you will have a url collision with variant 1. (We had
a similar problem trying to use /v3/publications/docker/)
variant 1: POST /pulp/v3/api/content/rpm/packages/copy/
content_units=[...] source="..." destination="..." [more params...]
Assuming that
Content copy between repositories is critically important to Katello
integration and is something that we have not really addressed yet. It
also needs to be completed before the RPM plugin can begin work on
depsolving. The story that results from this discussion should probably be
put on one of
