**Is your feature request related to a problem?
We manage 1000+ RPM repositories in the upstream-pulp server. During certain situations, we need to prioritize syncing a subset of repositories. However, the current process scans all repositories in upstream-pulp for changes, which is time-consuming and inefficient when only a few repositories need immediate synchronization.
** Describe the solution you'd like
Introduce support for passing pulp-labels as an argument to the upstream-pulp replication task. This would allow syncing only the repositories that match the specified labels, enabling prioritized and faster synchronization of critical repositories.
** Describe alternatives you've considered
As a workaround, we create separate upstream-pulp objects for different groups of repositories by assigning labels and setting the policy to labeled. We then execute the respective upstream-pulp object to sync only the required repositories. However, this approach increases management overhead and complexity.
**Is your feature request related to a problem?
We manage 1000+ RPM repositories in the upstream-pulp server. During certain situations, we need to prioritize syncing a subset of repositories. However, the current process scans all repositories in upstream-pulp for changes, which is time-consuming and inefficient when only a few repositories need immediate synchronization.
** Describe the solution you'd like
Introduce support for passing pulp-labels as an argument to the upstream-pulp replication task. This would allow syncing only the repositories that match the specified labels, enabling prioritized and faster synchronization of critical repositories.
** Describe alternatives you've considered
As a workaround, we create separate upstream-pulp objects for different groups of repositories by assigning labels and setting the policy to labeled. We then execute the respective upstream-pulp object to sync only the required repositories. However, this approach increases management overhead and complexity.