MET-89: Add an optional parameter limit-backups on patching stage #83
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ckups # Conflicts: # src/Patch/Task/CheckDiskSpaceHandler.php
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For Deployer we need an optional parameter limit-backups
This is needed so that we can better control the number of backups that are stored and limit the usage of disk space and inodes.
The intended functionality is to pass in an optional parameter when patching: limit-backups=5 and if the number of backups exceeds the limit, then the oldest packages will be deleted similarly to how the packages are deleted when there isn't enough disk space
Options