Generate release

[slashben]

Build Process Improvement:

• Changed the docker-push target in the Makefile to depend on docker-build, ensuring the image is built before pushing.

Summary by CodeRabbit

Release Notes

• New Features

  • Added trigger alert identification to rule failures, enabling detection of trigger-based alerts in the system

• Chores

  • Updated external dependencies
  • Enhanced Docker build workflow to ensure proper build sequence

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

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The changes introduce a new IsTriggerAlert boolean flag that propagates through the rule failure and alert pipeline. The flag is added to the GenericRuleFailure data structure with getter/setter methods, initialized during rule failure creation, and ultimately populated in HTTP-exported RuntimeAlert payloads. Additionally, the Makefile docker-push target is updated to depend on docker-build, and an external Go dependency is bumped to a newer version.

Changes

Cohort / File(s)	Summary
Build and Dependency Updates Makefile, go.mod	Makefile: docker-push target now depends on docker-build (previously standalone). go.mod: Updated armosec/armoapi-go dependency from v0.0.654 to v0.0.663
Rule Failure Flag Infrastructure pkg/rulemanager/types/failure.go	Added IsTriggerAlert field to GenericRuleFailure struct and implemented GetIsTriggerAlert() and SetIsTriggerAlert() methods on both the RuleFailure interface and GenericRuleFailure concrete type
Rule Failure Flag Propagation pkg/rulemanager/ruleadapters/creator.go, pkg/exporters/http_exporter.go	creator.go: Initializes IsTriggerAlert from rule.IsTriggerAlert in CreateRuleFailure. http_exporter.go: Populates IsTriggerAlert field in RuntimeAlert payload using failedRule.GetIsTriggerAlert()

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• feat: propagate IsTriggerAlert field from rules to runtime alerts #686: Directly related—both PRs modify the same code paths to propagate the IsTriggerAlert flag across rule failure types, creation, and alert export.

Suggested reviewers

• amirmalka

Poem

🐰 A flag hops through the system bright,
IsTriggerAlert set just right,
Through failures and exports it flows,
Docker builds before push goes,
Dependencies updated with care!

✨ Finishing touches

• 📝 Generate docstrings

---

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