Re: [Pulp-dev] signing service interface

On Wed, May 6, 2020 at 4:07 AM Matthias Dellweg wrote: > As i see it, it is up to the subclass (e.g. AptReleaseSigningService, > YumMetadataSigninigService, ...) to provide a stable interface. And the way > it is implemented, the script for an AptReleaseSigninigService is required > to report

Re: [Pulp-dev] the "relative path" problem

I'd like to provide a little bit more context for my previous email by going back to the original problem statement: On Wed, Apr 1, 2020 at 9:23 AM Daniel Alley wrote: > Problem: > > Currently, a relative_path is tied to content in Pulp. This means that if > a content unit exists in two places

[Pulp-dev] Pulp Container meeting notes

Pulp 3: - https://pulp.plan.io/issues/6315 pull secret - convert to Docs - [lubos] Add docs steps and test out that they work Pulp 2: - https://github.com/pulp/pulp_docker/pull/459 retry

Re: [Pulp-dev] Pulp 3 CLI MVP

On 5/6/20 10:57 AM, Dennis Kliban wrote: On Wed, May 6, 2020 at 12:30 PM David Davis > wrote: Matthias and I met today to go over some plans for a prototype. I wrote some notes[0] down. As part of the prototype, we'd propose two deliverables (one this

Re: [Pulp-dev] Pulp 3 CLI MVP

On Wed, May 6, 2020 at 12:30 PM David Davis wrote: > Matthias and I met today to go over some plans for a prototype. I wrote > some notes[0] down. As part of the prototype, we'd propose two deliverables > (one this week and one next week): > > 1. A set of ~2-3 click commands that use the

Re: [Pulp-dev] New pulpcore release (3.3.1?)

After our meeting today with Katello, we decided to release a 3.3.1 release this week with just https://pulp.plan.io/issues/6565 which is currently blocking them. There is a large backlog of fixes for 3.3 that probably cannot be cleanly picked onto the 3.3 branch. Moreover, we are coming up soon

Re: [Pulp-dev] Pulp 3 CLI MVP

Matthias and I met today to go over some plans for a prototype. I wrote some notes[0] down. As part of the prototype, we'd propose two deliverables (one this week and one next week): 1. A set of ~2-3 click commands that use the bindings to interact with Pulp 2. Some openapi-generator templates

[Pulp-dev] CI/CD meeting notes

May 6, 2020 - CI status check - https://travis-ci.org/github/pulp/pulp failing - Bug on sprint - https://travis-ci.com/github/pulp/pulpcore failing - https://travis-ci.com/github/pulp/pulpcore/jobs/328171522#L1081 -

Re: [Pulp-dev] New pulpcore release (3.3.1?)

When I look at the all_task_dispatched ticket I see a feature; the TaskGroup not being in the plugin API I can see as a bug. If we release a feature I think it would need to be 3.4.0. This is inconvenient I know, but my concern is that if a feature gets released in Z stream even with good

Re: [Pulp-dev] signing service interface

As i see it, it is up to the subclass (e.g. AptReleaseSigningService, YumMetadataSigninigService, ...) to provide a stable interface. And the way it is implemented, the script for an AptReleaseSigninigService is required to report the filenames of both created signatures. And that is verified by