pulp container pull-through
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 29
- Forks
- 45
- Avg merge
- 4h 45m
- Merged PRs (30d)
- 1
Description
Hi there!
I just wanted to make sure if I'm not getting something or if the rpm container pull-through configuration is really missing at the moment?
If yes: how would I go about to add it? I've seen that you also provide an "api_call" method that takes in the operation id of the api ... does it mean that I would need to do all the GET/POST/UPDATE calls myself? How hard would it be to add it using the PulpRemoteAnsibleModule?
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 the PulpRemoteAnsibleModule and the existing api_call approach mentioned in the issue. Determine how RPM container pull-through configuration should map to the required GET, POST, and update operations; the work is done when that configuration is supported without requiring callers to implement those operations themselves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, python
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100