Import/Export must include signatures related to exported content
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 62
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 37
Description
author: rochacbruno
original redmine issue: https://pulp.plan.io/issues/9545
The import/export plugin can either include all the signatures present in the system or gradually include only what is present on the exported content.
https://docs.pulpproject.org/pulpcore/workflows/import-export.html#exporting-specific-versions
Related to: https://pulp.plan.io/issues/9543
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 with the import/export plugin and the linked Pulp workflow for exporting specific versions, then review related issue 9543 for context. Determine how signatures associated with exported content should be selected and verify that the chosen behavior includes the required signatures during import/export.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100