fix(policy): add protocol/enforcement/tls to statsig and sentry endpoints#1220
Conversation
…ints Both statsig.anthropic.com and sentry.io define GET/POST rules but are missing protocol: rest, enforcement: enforce, and tls: terminate. Without these fields the proxy treats them as L4-only connections and the method rules are never evaluated. Closes NVIDIA#1214
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughNetwork policy configuration fields ( Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 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)
Comment |
|
Merging, but future PRs need DCO Signoff in PR body now |
…ints (#1220) ## Summary - Add missing `protocol: rest`, `enforcement: enforce`, and `tls: terminate` to `statsig.anthropic.com` and `sentry.io` endpoints in `openclaw-sandbox.yaml` ## Related Issue Closes #1214 ## Changes Both endpoints define GET/POST method rules, but without `protocol: rest` the proxy treats them as L4-only connections — the rules are never evaluated and any HTTP method is allowed through. The fix adds the same three fields that `api.anthropic.com` (the adjacent endpoint in the same policy group) already has: ```yaml protocol: rest enforcement: enforce tls: terminate ``` No new endpoints, no rule changes — just enabling L7 inspection on two endpoints that already have rules written for it. ## Testing - Verified the YAML structure matches the working `api.anthropic.com` endpoint pattern - No schema changes — `protocol`, `enforcement`, and `tls` are existing fields used across the policy file ## Checklist - [x] Conventional commit format - [x] Scoped to issue, no unrelated changes - [x] No secrets or credentials <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated network policy configurations for external service endpoints, including enhanced security enforcement and TLS termination settings. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: latenighthackathon <latenighthackathon@users.noreply.github.com> Co-authored-by: KJ <kejones@nvidia.com>
…ints (NVIDIA#1220) ## Summary - Add missing `protocol: rest`, `enforcement: enforce`, and `tls: terminate` to `statsig.anthropic.com` and `sentry.io` endpoints in `openclaw-sandbox.yaml` ## Related Issue Closes NVIDIA#1214 ## Changes Both endpoints define GET/POST method rules, but without `protocol: rest` the proxy treats them as L4-only connections — the rules are never evaluated and any HTTP method is allowed through. The fix adds the same three fields that `api.anthropic.com` (the adjacent endpoint in the same policy group) already has: ```yaml protocol: rest enforcement: enforce tls: terminate ``` No new endpoints, no rule changes — just enabling L7 inspection on two endpoints that already have rules written for it. ## Testing - Verified the YAML structure matches the working `api.anthropic.com` endpoint pattern - No schema changes — `protocol`, `enforcement`, and `tls` are existing fields used across the policy file ## Checklist - [x] Conventional commit format - [x] Scoped to issue, no unrelated changes - [x] No secrets or credentials <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated network policy configurations for external service endpoints, including enhanced security enforcement and TLS termination settings. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: latenighthackathon <latenighthackathon@users.noreply.github.com> Co-authored-by: KJ <kejones@nvidia.com>
…ints (NVIDIA#1220) ## Summary - Add missing `protocol: rest`, `enforcement: enforce`, and `tls: terminate` to `statsig.anthropic.com` and `sentry.io` endpoints in `openclaw-sandbox.yaml` ## Related Issue Closes NVIDIA#1214 ## Changes Both endpoints define GET/POST method rules, but without `protocol: rest` the proxy treats them as L4-only connections — the rules are never evaluated and any HTTP method is allowed through. The fix adds the same three fields that `api.anthropic.com` (the adjacent endpoint in the same policy group) already has: ```yaml protocol: rest enforcement: enforce tls: terminate ``` No new endpoints, no rule changes — just enabling L7 inspection on two endpoints that already have rules written for it. ## Testing - Verified the YAML structure matches the working `api.anthropic.com` endpoint pattern - No schema changes — `protocol`, `enforcement`, and `tls` are existing fields used across the policy file ## Checklist - [x] Conventional commit format - [x] Scoped to issue, no unrelated changes - [x] No secrets or credentials <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated network policy configurations for external service endpoints, including enhanced security enforcement and TLS termination settings. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: latenighthackathon <latenighthackathon@users.noreply.github.com> Co-authored-by: KJ <kejones@nvidia.com>
Summary
protocol: rest,enforcement: enforce, andtls: terminatetostatsig.anthropic.comandsentry.ioendpoints inopenclaw-sandbox.yamlRelated Issue
Closes #1214
Changes
Both endpoints define GET/POST method rules, but without
protocol: restthe proxy treats them as L4-only connections — the rules are never evaluated and any HTTP method is allowed through.The fix adds the same three fields that
api.anthropic.com(the adjacent endpoint in the same policy group) already has:No new endpoints, no rule changes — just enabling L7 inspection on two endpoints that already have rules written for it.
Testing
api.anthropic.comendpoint patternprotocol,enforcement, andtlsare existing fields used across the policy fileChecklist
Summary by CodeRabbit