As a user, I can enforce content specific uniqueness constaints in a repo version
RemoveDuplicates stage provides the opportunity to enforce uniqueness constraints for content at the sync time.
The duplicate problem can be encountered at any time content is added to a repository, not only at sync time.
E.g. Content was uploaded, or content was synced as a part of other repo, and now it's added/copied to a new repository.
It would be good if some check/validation happened for any added content, e.g. at this stage
Examples for where uniqueness might be needed in a repo version:
- only one content unit with a certain characteristics should be present in a repo (only one advisory with the same id, only one module_defaults for a module, etc)
This issue was discussed on this thread: https://www.redhat.com/archives/pulp-dev/2019-May/msg00061.html
On the plugin content model define a
repo_key - one or more fields which must be unique within a repo version.
Check uniqueness of the
repo_key for each added content type at the repository version creation time https://github.com/pulp/pulpcore/blob/aef490e201f89fc005ba3239fda3a79c05e28fd7/pulpcore/app/models/repository.py#L343.
Whether it's sync, copy, or upload,
repo_key uniqueness will be ensured if core/plugin devs use
with RepositoryVersion.create(...) context manager.
Added by bmbouter about 3 years ago
Add repo_key support for
Content model now supports a
repo_key attribute which defaults
to (). Plugin writers can specify this, and the tuple field names will
automatically replace another unit of the same type with these field
Required PR: https://github.com/pulp/pulp_file/pull/290