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

Quota based repositories #6109

Open
simenon opened this issue Dec 4, 2024 · 2 comments
Open

Quota based repositories #6109

simenon opened this issue Dec 4, 2024 · 2 comments
Labels

Comments

@simenon
Copy link
Contributor

simenon commented Dec 4, 2024

Is your feature request related to a problem? Please describe.
Sometimes we want to restrict the disk usage of a repository. Therefore it would be nice if we somehow can define a quota on repository size.

Describe the solution you'd like
Option to define a quota on a repository based on disksize and/or amount of packages

Describe alternatives you've considered
none

Additional context
We use build pipelines a lot that deploy their nightly builds. In time this can grow so large it fills the disk. To prevent this we would like to quota these kind of repositories

@gerrod3
Copy link
Contributor

gerrod3 commented Dec 4, 2024

What would be the behavior of the quota that you are looking for? Stop the packages from being added, remove old packages, combination of both?

While not what you asked for, currently you could set up a cron job to run the reclaim task on your nightly repositories if the content is no longer needed.

@simenon
Copy link
Contributor Author

simenon commented Dec 5, 2024

The default behavior of the quota would be blocking the upload.

I would not classify removal of packages a functionality of a quota. That would most likely fall under another clean up task where we can specify the criteria for removal, like older then x days or keep last 10 versions .

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