feat: propagate IsTriggerAlert field from rules to runtime alerts

[slashben]

Summary

Propagate the IsTriggerAlert field from runtime rules through to runtime alerts. This allows downstream consumers to identify trigger alerts.

Changes

• Update armoapi-go dependency to v0.0.663 (which includes IsTriggerAlert field in RuntimeAlert)
• Add IsTriggerAlert field to GenericRuleFailure struct
• Add GetIsTriggerAlert() and SetIsTriggerAlert() methods to RuleFailure interface
• Copy IsTriggerAlert from rule to failure in CreateRuleFailure()
• Copy IsTriggerAlert from failure to alert in createRuleAlert()

Data Flow

RuntimeRule.IsTriggerAlert
    ↓
GenericRuleFailure.IsTriggerAlert (copied in CreateRuleFailure)
    ↓
RuntimeAlert.IsTriggerAlert (copied in createRuleAlert)

Related PR

• feat: add IsTriggerAlert field to RuntimeAlert struct armosec/armoapi-go#593 - Added IsTriggerAlert field to RuntimeAlert struct

Backward Compatibility

• Uses omitempty tags so existing alerts without the field will continue to work
• The field defaults to false when not present

Summary by CodeRabbit

• Dependencies

  • Updated the armoapi-go dependency to v0.0.663.

• New Features

  • Added trigger alert identification and tracking capabilities throughout the system. Trigger alert information is now properly identified, tracked, and propagated across the rule failure evaluation and alert notification pipeline, ensuring comprehensive handling and visibility of all alert events in your environment.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes introduce a new IsTriggerAlert field that flows through the rule failure and alert system. Starting with a dependency version bump, the field is added to core type definitions with getter/setter methods, assigned during rule failure creation, and finally populated when exporting runtime alerts.

Changes

Cohort / File(s)	Summary
Dependency Update go.mod	Updated armoapi-go dependency from v0.0.654 to v0.0.663
Core Type Definitions pkg/rulemanager/types/failure.go	Added IsTriggerAlert bool field to GenericRuleFailure struct and defined GetIsTriggerAlert() and SetIsTriggerAlert() methods on both the RuleFailure interface and its implementation
Rule Failure Creation pkg/rulemanager/ruleadapters/creator.go	Populated IsTriggerAlert field in RuleFailure construction by assigning rule.IsTriggerAlert
Alert Export pkg/exporters/http_exporter.go	Populated IsTriggerAlert field in RuntimeAlert by calling failedRule.GetIsTriggerAlert()

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A trigger flag hops through the code so bright,
From rules to failures, shining in the night,
GetIsTriggerAlert—a query so divine,
Through exporters it travels, each field in line!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly and accurately summarizes the main change: propagating the IsTriggerAlert field from rules to runtime alerts, which is the core objective of all modifications across the five changed files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}