Forget-C
commented
9 months ago The original purpose was to abstract the filter framework to facilitate the addition of filter parameters. Other changes are necessary to achieve this goal. #187
now, If we want to add a filter, we only need the following steps：
create filter func
// FilterFunc is a filter that is a function
// If the resource is legal, return true
// example:
// deployment.Spec.Replicas > 0; return true
// meta.GetLabels()["kor/used"] == "true"; return true
type FilterFunc func(object runtime.Object, opts *Options) bool
func TestFilter(object runtime.Object, opts *Options) bool {
if meta, ok := object.(metav1.Object); ok {
if meta.GetLabels()["kor/used"] == "true" {
return true
}
}
return false
}Set a name
const TestFilterName = "test"Add to registry
func NewDefaultRegistry() Registry {
return Registry{
LabelFilterName: LabelFilter,
AgeFilterName: AgeFilter,
KorLabelFilterName: KorLabelFilter,
TestFilterName: TestFilter,
}
}
codecov-commenter
refactor&feat&fix&style:
kor.Optsand filter parametersfilters.Options.includeExcludeListsno longer participates incmd argsbinding, and is taken over byfilters.Options.includeNamespaceandexcludeNamespaceare taken over byfilters.Optionsand will only be executed once.kor/used=truetag.The unit tests have passed, but due to the large scope of the changes, more tests are needed.