Update imports API in v3
Open
Nobody has claimed this yet.
GalaxyNG
Issue
Migrated from Redmine
Severity: Medium
- Dominant language
- Python
- Stars
- 68
- Forks
- 62
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 37
Description
Author: @newswangerd (newswangerd)
Redmine Issue: 9048, https://pulp.plan.io/issues/9048
There are currently two implementations for the imports API in v3/imports and _ui/imports in galaxy ng. _ui/imports seems to be the one that is used by the UI, so v3/imports in pulp ansible needs to be updated to work like _ui/imports does in galaxy_ng`
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 comparing the v3/imports implementation in pulp_ansible with _ui/imports in galaxy_ng, focusing on how the UI implementation is used. Identify the behavior that must be matched, then verify that the v3 imports API works like the UI implementation; the issue does not name tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100