Skip to content

chore(deps): bump armoapi-go to v0.0.719#384

Open
matthyx wants to merge 1 commit into
mainfrom
feat/bump-armoapi-rule-openprotection
Open

chore(deps): bump armoapi-go to v0.0.719#384
matthyx wants to merge 1 commit into
mainfrom
feat/bump-armoapi-rule-openprotection

Conversation

@matthyx

@matthyx matthyx commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

What

Bumps github.com/armosec/armoapi-go from 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.UnionOpenProtection
  • the ProfileDataRequired schema

The follow-up watcher will resolve RuntimeRuleAlertBinding selectors against the rule library (armosec/rulelibrary, which requires armoapi ≥ v0.0.719) and publish the union of profileDataRequired.opens as 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:

  • Only armoapi-go moves in require; node-agent (v0.3.38) and storage (v0.0.239) compile unchanged against the newer armoapi — no coordinated bump needed.
  • go.mod change is one line; go.sum changes are 2 lines; no indirect requires added or removed.

Verification

  • go build ./... — clean
  • go vet ./... — clean (compiles all packages incl. tests)
  • go test ./watcher/... — pass

🤖 Generated with Claude Code

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>
@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@matthyx, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 42 minutes and 46 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 68f20170-9f20-40a6-b88a-580e367bfdf3

📥 Commits

Reviewing files that changed from the base of the PR and between 8f1c465 and e953a9e.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (1)
  • go.mod
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/bump-armoapi-rule-openprotection

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.

❤️ Share

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

@github-actions

Copy link
Copy Markdown

Summary:

  • License scan: success
  • Credentials scan: failure
  • Vulnerabilities scan: failure
  • Unit test: success
  • Go linting: failure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant