🌱 Allow multiple rules per validator

[mattwelke]

Summary

Plugins should support defining more than one rule of the same rule type per validator. For example, in the AWS plugin:

type AwsValidatorSpec struct {
...
	AmiRules []AmiRule `json:"amiRules,omitempty" yaml:"amiRules,omitempty"`
...
}

The Kubescape plugin should be changed to allow this too. Right now, its spec only allows one rule of each type per validator:

type KubescapeValidatorSpec struct {
...
	SeverityLimitRule SeverityLimitRule `json:"severityLimitRule,omitempty" yaml:"severityLimitRule,omitempty"`
...
	IgnoredCVERule []string `json:"ignoredCVERule,omitempty" yaml:"ignoredCVERule,omitempty"`
...
	FlaggedCVERule []FlaggedCVE `json:"flaggedCVERule,omitempty" yaml:"flaggedCVERule,omitempty"`
}

For example, SeverityLimitRule can be changed to []SeverityLimitRule to accomplish this.

After the spec is changed, the controller logic should be changed to iterate through each rule, processing them one at a time.

[TylerGillson]

@wcrum was working on a refactor to the plugin that I believe would address this. @wcrum can you please chime in?

[dosubot]

Hi, @mattwelke. I'm Dosu, and I'm helping the validator-plugin-kubescape team manage their backlog. I'm marking this issue as stale.

Issue Summary:

• You proposed an enhancement to allow multiple rules of the same type per validator in the Kubescape plugin.
• This would require changes to KubescapeValidatorSpec and updates to the controller logic.
• @TylerGillson mentioned that @wcrum was working on a refactor that might address this issue and requested input from @wcrum.

Next Steps:

• Could you confirm if this issue is still relevant with the latest version of the validator-plugin-kubescape repository? If so, please comment to keep the discussion open.
• If there is no further activity, this issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!