Pulp: Issueshttps://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-10-14T10:12:04ZPulp
Planio Container Support - Story #9507 (CLOSED - DUPLICATE): As a user I can sync container image with i...https://pulp.plan.io/issues/95072021-10-14T10:12:04Zipanova@redhat.comipanova@redhat.com
<p><strong>Ticket moved to GitHub</strong>: "pulp/pulp_container/498":<a href="https://github.com/pulp/pulp_container/issues/498" class="external">https://github.com/pulp/pulp_container/issues/498</a></p>
<hr>
<p>Synced signatures are not verified. Signature verification is offloaded to the client.</p>
<p>If <code>with-signature=True</code> ( TBD agree on naming) was specified only those images that have signature with be mirrored. Rest of the images will be skipped. <code>Signature server location</code> needs to be specified ( it's the webserver location of signatures, for example <a href="https://registry.redhat.io/containers/sigstore" class="external">https://registry.redhat.io/containers/sigstore</a>).
Otherwise it will be assumed that the signature is stored on the remote registry in a form of manifest or a separate object:</p>
<ul>
<li>If it is a separate object, signature API extensions should be available on the registry and <code>X-Registry-Supports-Signatures</code> header will identify that <a href="https://github.com/containers/image/blob/main/docs/signature-protocols.md#openshift-dockerdistribution-api-extension" class="external">https://github.com/containers/image/blob/main/docs/signature-protocols.md#openshift-dockerdistribution-api-extension</a>
</li>
<li>If it is stored in a form of a manifest then it most likely was signed with cosign <a href="https://github.com/SigStore/cosign#signing-subjects" class="external">https://github.com/SigStore/cosign#signing-subjects</a>. <strong>we will not support this for now</strong>
</li>
</ul>
<p><strong>Q:</strong> does podman/skopeo support verification of cosign signature type? Only atomic type for now <a href="https://github.com/containers/image/blob/main/docs/containers-signature.5.md#criticaltype" class="external">https://github.com/containers/image/blob/main/docs/containers-signature.5.md#criticaltype</a></p>
<p><strong>Q:</strong> how this will work with mirror=True?</p> File Support - Task #9289 (CLOSED - COMPLETE): Port pulp-manifest tool from pulp 2 to pulp 3https://pulp.plan.io/issues/92892021-08-24T17:09:50Zttereshcttereshc@redhat.com
<p>Upstream and downstream folks find the tool quite useful.
We should have pulp-manifest available in pulp 3 repositories:</p>
<ul>
<li>to make it clear that it works with pulp 3 as well (it looks like it should work as is)</li>
<li>to have a more logical place for it (currently it's in pulp_rpm in pulp2 branches)</li>
<li>to make it easier for katello to package it</li>
</ul>
<p>It can be in a dedicated repository or a part of pulp_file repo.<br>
Current location: <a href="https://github.com/pulp/pulp_rpm/tree/2.21-release/pulp_manifest" class="external">https://github.com/pulp/pulp_rpm/tree/2.21-release/pulp_manifest</a></p> Migration Plugin - Task #8892 (CLOSED - COMPLETE): Release 0.11.2https://pulp.plan.io/issues/88922021-06-14T09:15:39Zttereshcttereshc@redhat.comMigration Plugin - Task #8693 (CLOSED - COMPLETE): Release 0.11.1https://pulp.plan.io/issues/86932021-05-04T12:25:43Zttereshcttereshc@redhat.comFile Support - Task #8355 (CLOSED - COMPLETE): Release 1.6.0https://pulp.plan.io/issues/83552021-03-05T15:36:07Zttereshcttereshc@redhat.comContainer Support - Story #8017 (CLOSED - CURRENTRELEASE): RBAC: Add access policy for container ...https://pulp.plan.io/issues/80172020-12-21T16:01:18Zipanova@redhat.comipanova@redhat.com
<p>Add RBAC for ContainerPushRepositoryVersion
<a href="https://docs.pulpproject.org/pulpcore/plugins/plugin-writer/concepts/rbac/overview.html#getting-started" class="external">https://docs.pulpproject.org/pulpcore/plugins/plugin-writer/concepts/rbac/overview.html#getting-started</a></p>
<p>ContainerRepoVersion inherits from regular RepoVersionViewset so that policy should probably be define in core.</p> Container Support - Story #7968 (CLOSED - CURRENTRELEASE): RBAC: Add access policy for container ...https://pulp.plan.io/issues/79682020-12-10T12:12:05Zipanova@redhat.comipanova@redhat.com
<p>Add RBAC for ContainerPushRepository
<a href="https://docs.pulpproject.org/pulpcore/plugins/plugin-writer/concepts/rbac/overview.html#getting-started" class="external">https://docs.pulpproject.org/pulpcore/plugins/plugin-writer/concepts/rbac/overview.html#getting-started</a></p> File Support - Task #7437 (CLOSED - CURRENTRELEASE): Require each pulp_file feature or bugfix to ...https://pulp.plan.io/issues/74372020-09-01T15:16:36Zbmbouterbmbouter@redhat.com
<a name="Background"></a>
<h2 >Background<a href="#Background" class="wiki-anchor">¶</a></h2>
<p>It would be great if each fix or feature came with a test asserting that fix/feature is working with the same commit as the fix or feature. This was originally proposed on pulp-dev <a href="https://www.redhat.com/archives/pulp-dev/2020-August/msg00053.html" class="external">here</a></p>
<a name="Todo"></a>
<h2 >Todo<a href="#Todo" class="wiki-anchor">¶</a></h2>
<ol>
<li>Add the functional test requirement to this page: <a href="https://pulp-file.readthedocs.io/en/latest/contributing.html" class="external">https://pulp-file.readthedocs.io/en/latest/contributing.html</a>
</li>
</ol> Pulp - Story #4054 (CLOSED - WONTFIX): Study Pulp data modelhttps://pulp.plan.io/issues/40542018-10-02T08:30:56Zvdusek
<p>Study Pulp data model to be able to compare Git and Pulp versioning. Start with reading<br>
these discussions: <a href="https://pulp.plan.io/issues/3360" class="external">#3360</a>, <a href="https://pulp.plan.io/issues/3842" class="external">#3842</a>, <a href="https://www.redhat.com/archives/pulp-dev/2017-December/msg00075.html" class="external">pulp-dev/2017-December/msg00075</a>.</p> Pulp - Task #3979 (CLOSED - CURRENTRELEASE): remove id field from all serializershttps://pulp.plan.io/issues/39792018-09-05T20:15:17Zdkliban@redhat.com
<p>Story 3850 is complete and Pulp returns shorter hrefs. The OpenAPI schema uses hrefs as identifiers. However, our REST API still returns 'id' with all the resources. To prevent users from getting confused about which field is the identifier for the resource, the id should be omitted from the response.</p> Pulp - Story #3944 (CLOSED - CURRENTRELEASE): Rename sync_mode and change its typehttps://pulp.plan.io/issues/39442018-08-29T14:30:52Zvdusek
<p>According to the pulp-dev mailing list discussion. Rename sync_mode param to mirror, change its type from string to boolean and change all the necessary logic in the code.</p> File Support - Story #3913 (CLOSED - CURRENTRELEASE): As a user I can specify the manifest filena...https://pulp.plan.io/issues/39132018-08-13T15:24:44Zdaviddavis
<p>Currently, the filename is hardcoded as PULP_MANIFEST. Allow users to specify a filename on the file publisher to be used when publishing. Optimally, the default should be the same as in <a class="issue tracker-3 status-11 priority-6 priority-default closed" title="Story: As a user, I can specify the file manifest name on the remote when syncing and publishing a repos... (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/3912">#3912</a> (ie manifest.csv).</p> File Support - Story #3912 (CLOSED - CURRENTRELEASE): As a user, I can specify the file manifest ...https://pulp.plan.io/issues/39122018-08-13T15:23:03Zdaviddavis
<p>Currently, we require users to specify the full url to the PULP_MANIFEST file. This is a bit at odds with how Pulp 2 and other plugins work so instead, we'd like to add a separate field in which users can specify the filename of the remote manifest.</p> File Support - Task #3494 (CLOSED - WONTFIX): Add sync_mode parameter to endpoint that deploys sy...https://pulp.plan.io/issues/34942018-03-16T13:21:20Zamacdona@redhat.comaustin@redhat.com
<p>sync_mode will be removed in <a href="https://pulp.plan.io/issues/3492" class="external">https://pulp.plan.io/issues/3492</a>, which will break sync.</p> Pulp - Story #1317 (CLOSED - WONTFIX): allow to host npm contenthttps://pulp.plan.io/issues/13172015-10-16T14:48:02Zmsuchy@redhat.commsuchy@redhat.com
<p>As part of Software Pipeline project in Red Hat, we would like to use Pulp as repository for various upstream packages.</p>
<p>AFAIK Pulp is unable to host those native formats. So we are forced to use another solution. Likely Sonatype Nexus.<br>
It would be nice if you can support those formats in close feature, so we can use Pulp only.</p>
<p>I understand that this is being worked on, so adding for tracking pourposes.</p>