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

As a user, I can have Pulp download content for a repository version #1976

Open
pulpbot opened this issue Jan 17, 2022 · 2 comments
Open

As a user, I can have Pulp download content for a repository version #1976

pulpbot opened this issue Jan 17, 2022 · 2 comments
Labels

Comments

@pulpbot
Copy link
Member

pulpbot commented Jan 17, 2022

Author: daviddavis (daviddavis)

Redmine Issue: 8324, https://pulp.plan.io/issues/8324


Problem

Consider the following use cases:

  1. You want to export a particular repository content but some of its content is on-demand which will cause the export to fail
  2. You want to lockdown your allowed content checksums but a particular repository version has remote content with undesired checksums (e.g. md5, sha1)

The current solution we recommend to users is to switch their remote to immediate and sync. This can be problematic for several reasons: maybe your repo version is old and you don't remember the remote you used to create it; maybe it was created from multiple remotes; maybe you don't want to update your remotes' policies; maybe creating a new repo version for your repo is undesirable; etc.

Pulp 2 provided this functionality (pulp-admin repo download --repo-id=zoo) and Satellite Support has asked for this in Pulp 3 so I believe there would be some value in such a feature.

Solution

I suggest we create a way that a user can trigger a download for a specific RepositoryVersion (or maybe even RepositoryVersions) so that its content gets downloaded to storage.

@stale
Copy link

stale bot commented May 24, 2022

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

@stale stale bot added the stale label May 24, 2022
@dralley dralley removed the stale label May 25, 2022
@stale
Copy link

stale bot commented May 25, 2022

This issue is no longer marked for closure.

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

2 participants