Validate the requirements.yml file
Open
Nobody has claimed this yet.
Issue
Migrated from Redmine
Severity: Medium
- Dominant language
- Python
- Stars
- 68
- Forks
- 62
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 37
Description
Author: daviddavis (daviddavis)
Redmine Issue: 7734, https://pulp.plan.io/issues/7734
Validate the requirements.yml when a remote is saved.
Some examples:
- Validate the presence of required keys (name, source) if the entry is a hash
- Validate that
typematches up with whatever types we support (ie only galaxy at this point)
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
Start by locating the remote-save path that processes requirements.yml. Check how entries are represented, then verify that hash entries require name and source and that type is limited to the supported Galaxy type; done means invalid files are rejected when the remote is saved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100