Need a `dry-run` option for export similar to imports
Open
Nobody has claimed this yet.
Feature
Katello
satellite
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: paji@redhat.com (paji@redhat.com)
Bugzilla: https://bugzilla.redhat.com/buglist.cgi?quicksearch=1990472
Redmine Issue: 9214, https://pulp.plan.io/issues/9214
Pulp provides a nice dry run api when importing that cheks things like
- Importing archive files are in the right place
- Have the right perms
- repositories exist etc.
We need a similar api for the exports
- Check if the export stuff has the correct perms
- Export path is in the EXPORT_PATH
- Export has enough disk space
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
Review the existing import dry-run API and the export implementation first; the issue does not name files or tests. Done means an export dry run checks permissions, whether the export path is allowed, and available disk space.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 43/100