theupdateframework / theupdateframework/python-tuf
Add some more generated metadata files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 304
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 17
Description
#1915 adds metadata generation (with stored expected results). We should expand the collection in two directions:
- The current metadata is basically all with default values: Add More variation on the metadata (different key types, delegations, targets, etc)
- Include actual repositories (that are confirmed to work as repositories), possibly with several versions of the same repository: Note that we should be careful not to duplicate the code in RepositorySimulator based updater tests: possibly we could just make RepositorySimulator generated data reproducible and store the results of the RepositorySimulator runs (see the --dump option for related tests)
I'll assign to myself: I'll probably handle the first item and file a new issue on the second but let's see...
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 reading #1915 and its stored expected metadata results to understand the current generated collection. Then inspect RepositorySimulator and the --dump option in the related tests, as the issue suggests these may provide reproducible repository data. Done means expanding metadata variation and considering confirmed repository examples without duplicating updater-test data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100