Auto-refresh api-spec for other than version-changes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 43
- Forks
- 52
- Avg merge
- 11h 38m
- Merged PRs (30d)
- 11
Description
Currently we will auto-update api-spec if we notice that the pulp-instance you're pointing at, is running different versions than when last we refreshed the spec.
However - there are other ways for a spec to be invalid. If one instance has domains enabled, for example, and a second one running the same versions does not, their specs will not match.
We should trigger auto-refresh on more than just the version-list.
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 tracing the existing api-spec auto-refresh logic that compares version lists. Identify how instance capabilities such as domains enabled can make specs differ even when versions match. Done means refreshes are triggered for relevant spec-invalidating differences beyond version changes, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100