Project

Profile

Help

Task #7536

closed

Add support for ALLOWED_CONTENT_CHECKSUMS

Added by daviddavis about 4 years ago. Updated almost 4 years ago.

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

0%

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

Description

A couple use cases:

  • The migration should alert users if they try to upgrade a repository that's using a checksum not in ALLOWED_CONTENT_CHECKSUMS
  • Not sure if the migration plugin calculates checksums but if so, the migration should only use ones in ALLOWED_CONTENT_CHECKSUMS

There may be other use cases too?


Related issues

Related to Pulp - Story #5216: As a user, I can configure which checksum types I want to use in PulpCLOSED - CURRENTRELEASEggainey

Actions
Is duplicate of Migration Plugin - Task #7782: Ensure migration plugin runs in FIPS mode and respects the ALLOWED_CONTENT_CHECKSUMS configuraitonCLOSED - COMPLETEggainey

Actions

Also available in: Atom PDF