Stop publishing bindings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Bindings for pulp are too fragile as they depend on the combinations of pulpcore and plugin versions and even on some settings. So we cannot possibly publish any sort of autogenerated bindings that serves all installations.
We should simply stop publishing them and let users create them for their individual systems. Also we should promote using pulp-glue instead.
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 workflow or release entry point that publishes autogenerated bindings, then review how pulpcore and plugin versions and settings affect them. Check how pulp-glue is currently presented. Done means autogenerated bindings are no longer published and users are directed toward creating bindings for their individual systems and using pulp-glue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100