As a user, I can select the hasher types available per-domain instead of system-wide
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Currently you can use settings to tell Pulp which hashers can (and can't) be used. This is primarily for FIPS related use cases.
This RFE is requesting that a user can configure this per-domain. We have a limited number of domains who (for reasons totally beyond their control) have to sync RPM repos with SHA1 checksums. To me, ideal situation would be:
If unspecified, the existing system-wide defaults prevail (the existing settings), but a domain can have an optional config (somehow) that allows that domain to override the allowed checksums config.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or implementation entry points are named. Start by locating the existing system-wide hasher settings and the domain configuration model or API, then determine how an optional per-domain override can fall back to those defaults; done means domain-specific allowed hashers work without changing unspecified domains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100