As a user, Pulp prevents me from exporting a repo version when I should be exporting a publication
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: daviddavis (daviddavis)
Redmine Issue: 9142, https://pulp.plan.io/issues/9142
When exporting content to the filesystem or rsyncing it to a server, users will want to export a repo version (if the plugin doesn't have publications) or a publication (if the plugin has publications).
We need a way for plugin writers to indicate this and for the export code to check whether it should prevent users from exporting a repo version.
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
No file or test is named. Start by tracing the export code and the plugin-writer interfaces it consults; determine how repository versions and publications are represented and where an export should be prevented. Done means plugins can indicate the appropriate export target and the export path enforces that choice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100