Project

Profile

Help

Story #4458

closed

Story #5114: [Epic] Publish features

As a user, I can configure which checksum algorithm to use when creating metadata

Added by ttereshc about 5 years ago. Updated almost 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Katello
Sprint:
Sprint 70
Quarter:

Description

Support metadata_checksum_type and package_checksum_type options at publish time.
These are one-time options and are passed as a parameter for a publication creation call.
metadata_checksum_type affects all the repodata, including primary.xml, repomd.xml, etc.
package_checksum_type affects package checksum type in all repo metadata files.

Origin of checksum types and their precedence (at the top is the one which is used first if present and available):
- configuration at publish time
- a remote repo (store the checksum type from the remote source on the repository version model)
- Pulp default (sha256)

DNF supports different package checksum types in one repo.

Publication creation should never fail due to checksum type configuration. At least one checksum type is always available for a package and it should be used if the requested one is not available.


Related issues

Related to RPM Support - Test #4469: Test checksum algorithm when publishingCLOSED - COMPLETEActions

Also available in: Atom PDF