Story #3657
closedAs a user I can manage modulemd content
100%
Description
As a result of this story it will be possible to sync, upload, publish, copy and remove modulemd
Upload:
We will accept a compressed yaml doc file which might have 1 or more modules. We will not check for the presence of the modular rpms in the destination repo
Sync:
We will parse a compressed yaml doc file which might have 1 or more modules. We will not check for the presence of the modular rpms in the destination repo
Publish:
We will successfully publish all modules, even those which are missing rpms. DNF-like clients are expected to fail gracefully in case of corrupted modules.
Copy:
Default copy will be simple copy. It will copy just the module itself. No rpms are carried over.
Remove:
Default remove will be simple remove. It will remove just the module itself. No rpms are touched.
For later: an option will be added '--recursive' which will will remove the module and it's rpms in case those rpms are not referenced in the other modules within the repo.
NOTE:
- in the pulp repo modular and not modular rpms can co-exist.
- we cannot prevent from removal of rpms which can be part of a module.
Related issues
Updated by ipanova@redhat.com over 6 years ago
- Related to Story #3206: Support for module metadata in pulp_rpm added
Updated by ipanova@redhat.com over 6 years ago
Based on some more discussion looks like we will need to support right away `smart removal` which will consist into module removal + its rpms which are not referenced in other modules within the repo.
Updated by ttereshc over 6 years ago
- Subject changed from As a user i can manage modulemd content to As a user I can manage modulemd content
- Groomed changed from No to Yes
Updated by ipanova@redhat.com over 6 years ago
- Sprint Candidate changed from No to Yes
Updated by ttereshc over 6 years ago
- Blocks Story #3659: Add a migration for transition from basic to advanced modular support added
Updated by ttereshc over 6 years ago
- Sprint changed from Sprint 38 to Sprint 39
Updated by jortel@redhat.com over 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to jortel@redhat.com
Updated by rchan over 6 years ago
- Sprint/Milestone set to 2.17.0
Adding to 2.17.0 milestone. This is one of the required deliverables.
Updated by dkliban@redhat.com over 6 years ago
- Sprint changed from Sprint 39 to Sprint 40
Updated by ipanova@redhat.com over 6 years ago
- Status changed from ASSIGNED to MODIFIED
Updated by ipanova@redhat.com over 6 years ago
- Platform Release changed from 2.17.0 to master
Updated by ipanova@redhat.com over 6 years ago
- Platform Release deleted (
master)
Updated by ipanova@redhat.com over 6 years ago
- Status changed from MODIFIED to 5
Updated by ipanova@redhat.com about 6 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE