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

✨ Rule filtering for validator rules check #140

Open
TylerGillson opened this issue Aug 7, 2024 · 1 comment
Open

✨ Rule filtering for validator rules check #140

TylerGillson opened this issue Aug 7, 2024 · 1 comment
Assignees
Labels
new-feature Net-new feature

Comments

@TylerGillson
Copy link
Member

TylerGillson commented Aug 7, 2024

Summary

Filter rules to be executed (within a single config file) by:

  • rule name (1 rule)
  • plugin (all rules for a plugin)
  • plugin rule type (all rules for a plugin of a specific rule type, e.g. DNSRules for the Network plugin)
    • Select plugin code + plugin rule type

E.g., validator check --direct --filter=name=dns-rule-1 --filter=plugin=AWS

@TylerGillson TylerGillson added the new-feature Net-new feature label Aug 7, 2024
@ahmad-ibra ahmad-ibra changed the title ✨ Rule filtering for validator check --direct ✨ Rule filtering for validator rules check Aug 17, 2024
Copy link

dosubot bot commented Nov 19, 2024

Hi, @TylerGillson. I'm Dosu, and I'm helping the validatorctl team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • Enhancement proposed for validator rules check command.
  • Suggestion to add filtering by rule name, plugin, or plugin rule type.
  • Aims to enable targeted and efficient rule execution.
  • No further comments or activity since the proposal.

Next Steps:

  • Is this issue still relevant to the latest version of the validatorctl repository? If so, please comment to keep the discussion open.
  • If there is no further activity, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

@dosubot dosubot bot added the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 19, 2024
@TylerGillson TylerGillson removed the stale Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-feature Net-new feature
Projects
None yet
Development

No branches or pull requests

2 participants