Split off rule criteria
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to split off the rule criteria so we can code our own and return a true/false back into the rule engine. This would allow more advanced checking that could be included in packs.
Example. Check to see if an open ticket already exists in your ticketing system.
I know I can do this in either a custom sensor or action, but it makes more sense to be in the criteria section of the rules.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the rule engine's criteria handling and how custom sensors, actions, and packs currently integrate with rules. Define the scope and interface for externally evaluated criteria, including how a true/false result is returned and tested. Done should include an agreed design and support for advanced checks such as detecting an existing ticket.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100