chore(deps): bump armoapi-go to v0.0.719#384
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe direct Go module dependency Changesarmoapi-go Dependency Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Summary:
|
Modernize the operator's armoapi-go from v0.0.673 to v0.0.719 to pick up the rule open-protection types (armotypes.OpenMatchers / UnionOpenProtection, ProfileDataRequired schema). This unblocks a follow-up watcher that resolves RuntimeRuleAlertBinding selectors against the rule library and publishes the union of profileDataRequired.opens for the storage apiserver. The bump is additive: node-agent (v0.3.38) and storage (v0.0.239) compile unchanged against the newer armoapi, so no coordinated bump is required here. go build, go vet, and the watcher test suite all pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Matthias Bertschy <matthias.bertschy@gmail.com> # Conflicts: # go.mod # go.sum
e953a9e to
c5fb1fb
Compare
|
Summary:
|
What
Bumps
github.com/armosec/armoapi-gofrom v0.0.673 → v0.0.719.Why
This is the dep-modernization step ahead of a rule open-protection watcher. v0.0.719 adds the types that watcher needs:
armotypes.OpenMatchers+armotypes.UnionOpenProtectionProfileDataRequiredschemaThe follow-up watcher will resolve
RuntimeRuleAlertBindingselectors against the rule library (armosec/rulelibrary, which requires armoapi ≥ v0.0.719) and publish the union ofprofileDataRequired.opensas a ConfigMap that the storage apiserver reads to keep sensitive-file rules (e.g. R0010) working through profile generalisation. Keeping the version bump as its own PR isolates the dependency change from the feature.Scope / cascade
Minimal and additive:
armoapi-gomoves inrequire; node-agent (v0.3.38) and storage (v0.0.239) compile unchanged against the newer armoapi — no coordinated bump needed.go.modchange is one line;go.sumchanges are 2 lines; no indirect requires added or removed.Verification
go build ./...— cleango vet ./...— clean (compiles all packages incl. tests)go test ./watcher/...— pass🤖 Generated with Claude Code
Summary by CodeRabbit