During the pulp_rpm meeting today @ttereshc identified that the on-demand
content concern I brought up is not an issue because modulemd is a metadata
file so it will always be downloaded and its Artifact saved regardless of
the on-demand policy. So that's a non-issue. :)
@mdellweg I will think
I am not entirely sure, whether it is the same kind of problem, but in
[0] there is an example of a stage that adds a declarative artifact in
the middle of the pipeline.
[0]
https://github.com/pulp/pulp_deb/blob/master/pulp_deb/app/tasks/synchronizing.py#L204
On Thu, 29 Aug 2019 10:42:33 -0400
I agree Austin's suggestion of a mechanism like that sounds good. Can a
more detailed description be written in Redmine and sent to the list? This
change is in Stages API which has such broad impact that I'd feel most
comfortable if we could get to that level of detail together somehow.
The
Austin, thank you.
Your option is more explicit, so it's probably better.
Tanya
On Wed, Aug 28, 2019 at 6:38 PM Austin Macdonald
wrote:
>
>
> On Wed, Aug 28, 2019 at 11:34 AM Tatiana Tereshchenko
> wrote:
>
>> Bump.
>>
>> Please provide feedback if you have any.
>> I'll start working on the
On Wed, Aug 28, 2019 at 11:34 AM Tatiana Tereshchenko
wrote:
> Bump.
>
> Please provide feedback if you have any.
> I'll start working on the PR to make the suggested change this week
> otherwise.
>
> Thank you,
> Tanya
>
> On Mon, Aug 26, 2019 at 12:46 PM Tatiana Tereshchenko
> wrote:
>
>> In
Bump.
Please provide feedback if you have any.
I'll start working on the PR to make the suggested change this week
otherwise.
Thank you,
Tanya
On Mon, Aug 26, 2019 at 12:46 PM Tatiana Tereshchenko
wrote:
> In RPM plugin we have Modulemd content. It comes from metadata as one file
> and we
In RPM plugin we have Modulemd content. It comes from metadata as one file
and we parse it and then save each modulemd as a separate file/artifact.
The question is how to handle this content in the sync pipeline.
Modulemd content is artifactless on a remote source (metadata) but it's not
