Actions
Task #7536
closed
Add support for ALLOWED_CONTENT_CHECKSUMS
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
Updated by daviddavis over 4 years ago
- Related to Story #7487: As a user, I'm prevented from changing ALLOWED_CONTENT_CHECKSUMS if I already have content in my DB added
Updated by daviddavis over 4 years ago
- Related to deleted (Story #7487: As a user, I'm prevented from changing ALLOWED_CONTENT_CHECKSUMS if I already have content in my DB)
Updated by daviddavis over 4 years ago
- Related to Story #5216: As a user, I can configure which checksum types I want to use in Pulp added
Updated by daviddavis about 4 years ago
- Is duplicate of Task #7782: Ensure migration plugin runs in FIPS mode and respects the ALLOWED_CONTENT_CHECKSUMS configuraiton added
Updated by daviddavis about 4 years ago
- Status changed from NEW to CLOSED - DUPLICATE
Actions
.