Project

Profile

Help

Story #5510

I would like to have an option to associate key-value pair to repository - former "Notes" field in Pulp 2

Added by Skullman about 1 year ago. Updated 27 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

When we distribute official RH repositories in RHUI, we are providing them with GPG keys to validate signature of RPMs present in them. It makes sense to have this information connected to particular repository as there are options to have custom repositories with RPMs that are not signed.

Original Pulp 2 field looks like this:
'notes':
{'_repo-type': 'rpm-repo',
'redhat-gpg-key': '/etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release'},


Related issues

Related to Pulp - Story #7127: Add object labelsNEW

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by fao89 about 1 year ago

  • Tracker changed from Issue to Story
  • Sprint/Milestone deleted (3.0.0)
  • % Done set to 0

#2 Updated by rchan 4 months ago

Skullman - Is this the only use case for this field? Please ping us when are ready to start collaborating on the solution for this and we'll make sure all use cases are understood before we figure out a solution.

#3 Updated by rchan 4 months ago

Slightly related, we have provided ability to sign repos: https://pulp.plan.io/issues/4812

Also here is another related issue: https://pulp.plan.io/issues/6926

#4 Updated by rchan 4 months ago

We have a feature request to be able to sign and verify content. That feature has not been prioritized, but if such a feature is required by multiple stakeholders, we may want to look at providing this within Pulp vs. just providing the ability to store a gpg key.

#6 Updated by sskracic 27 days ago

From RHUI team: key/value labeling of repositories is a must for RHUI4, as we need a way to store couple of attributes on per-repository basis:

  • GPG key used for contained RPMs, if any
  • base_path this repo is published under
  • checksum_type (SHA1 or SHA256)
  • repository group ("Red Hat", "custom", but could be few others)
  • boolean whether this repo is protected and needs a cert to be accessed
  • custom entitlement path for custom repos

There might be a couple of others as well that could pop up during the RHUI4 development.

#7 Updated by ipanova@redhat.com 20 days ago

Please register to edit this issue

Also available in: Atom PDF