Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance replicate feature #5214

Open
PotentialIngenuity opened this issue Apr 1, 2024 · 2 comments
Open

Enhance replicate feature #5214

PotentialIngenuity opened this issue Apr 1, 2024 · 2 comments
Labels

Comments

@PotentialIngenuity
Copy link

Is your feature request related to a problem? Please describe.
I performed a replicate with a tag filter and found that it deleted every remote/repository/distribution that didnt match the filter. This is not how I would expect the feature to work.

We have several repos we mirror from public repos that get updated once a week. We also have internal repos that get pushed to irregularly. We would like to replicate these repos separately but we currently cannot since anything outside of the filter gets deleted.

Describe the solution you'd like
I think it should never touch anything outside of the filter. Only change what the user is targeting. The removal step could still be run for the filtered content just don't remove anything outside of the filter.

@mdellweg
Copy link
Member

mdellweg commented Apr 2, 2024

This is how the replicate feature was designed and I'm unsure we can actually change that. The idea is that a replica is an hands off box that just fully mirrors a selected subset of upstream distributions.
I think, you can however limit its reach to a domain (given all your plugins already support that).

In case you need much more control, consider writing an ansible playbook a bit like this: mdellweg/squeezer@f426142

@dkliban
Copy link
Member

dkliban commented May 10, 2024

It would be better if the replicate task would create on the replicate Pulp, the pulp labels that are specified in the UpstreamPulp config. THen when the repositories, remotes, and distributions are created, these labels are applied to them. In subsequent runs of the replicate task, the replicate will only consider local repositories with the labels. All other repositories will not be affected by the replicate task. This will allow users to run replicate on a subset of repositories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants