-
Notifications
You must be signed in to change notification settings - Fork 42
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
change prune strategy to separate resource removal from the strategy … #76
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Pull Request Test Coverage Report for Build 1394911945
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah nice. Basically you get the resources by a particular strategy then do the removal in one place. I like it.
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there is a bug with the max count strategy, details in comments on the file.
return err | ||
} | ||
default: | ||
return fmt.Errorf("unsupported resource kind") | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can move each error check to a single one after the switch
Description of the change:
this change separates out the removal of resources logic from the various prune strategy implementations so that someone writing a custom strategy doesn't have to worry about implementing or calling resource removal logic themselves.
Motivation for the change:
this should make it easier for custom strategy implementations to be developed since they would not have to remember to call resource removal logic directly.