fix(policy): remove deprecated tls: terminate from all policy presets#1885
fix(policy): remove deprecated tls: terminate from all policy presets#1885BenediktSchackenberg wants to merge 2 commits intoNVIDIA:mainfrom
Conversation
OpenShell 0.0.24+ deprecated the tls: terminate field. Keeping it generates WARN-level log entries on every sandbox start and may interfere with CONNECT tunnel handling in some proxy configurations. Removed from all affected files: - nemoclaw-blueprint/policies/openclaw-sandbox.yaml (12 instances) - presets/brave.yaml, huggingface.yaml, jira.yaml, npm.yaml, outlook.yaml, pypi.yaml Fixes NVIDIA#1686 Signed-off-by: Benedikt Schackenberg <6381261+BenediktSchackenberg@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughRemoved deprecated Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 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 |
There was a problem hiding this comment.
Pull request overview
Removes deprecated tls: terminate entries from NemoClaw policy presets / blueprint policy to avoid OpenShell WARN spam and reduce the risk of interfering with CONNECT tunnel behavior.
Changes:
- Removed
tls: terminatefromnemoclaw-blueprint/policies/openclaw-sandbox.yaml. - Removed
tls: terminatefrom multiple preset policy YAMLs (brave, huggingface, jira, npm, outlook, pypi).
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| nemoclaw-blueprint/policies/presets/pypi.yaml | Drops deprecated tls: terminate from PyPI endpoints. |
| nemoclaw-blueprint/policies/presets/outlook.yaml | Drops deprecated tls: terminate from Outlook endpoints. |
| nemoclaw-blueprint/policies/presets/npm.yaml | Drops deprecated tls: terminate from npm/Yarn registry endpoints. |
| nemoclaw-blueprint/policies/presets/jira.yaml | Drops deprecated tls: terminate from Jira endpoints. |
| nemoclaw-blueprint/policies/presets/huggingface.yaml | Drops deprecated tls: terminate from Hugging Face endpoints. |
| nemoclaw-blueprint/policies/presets/brave.yaml | Drops deprecated tls: terminate from Brave endpoints. |
| nemoclaw-blueprint/policies/openclaw-sandbox.yaml | Drops deprecated tls: terminate from the default OpenClaw sandbox policy. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| port: 443 | ||
| protocol: rest | ||
| enforcement: enforce | ||
| tls: terminate | ||
| rules: | ||
| - allow: { method: POST, path: "/v1/messages" } |
There was a problem hiding this comment.
The PR description/title indicates tls: terminate has been removed from all affected policy presets/files, but the repo still contains multiple tls: terminate entries in agents/hermes/policy-additions.yaml (used via policyAdditionsPath in src/lib/agent-defs.ts). If the goal is to eliminate WARN logs globally (and fully resolve #1686), consider removing it there too or clarifying the PR scope/description that Hermes is intentionally out of scope.
Missed in the initial sweep — agents/hermes/policy-additions.yaml contained 13 more tls: terminate entries. Per Copilot review on NVIDIA#1885. Signed-off-by: Benedikt Schackenberg <6381261+BenediktSchackenberg@users.noreply.github.com>
|
Fixed — also removed |
|
@BenediktSchackenberg Heads up — #1821 addresses the same issue (#1686) with the same file changes, and also adds a regression test in Your contribution is still appreciated — the cleanup is correct. Just a timing overlap. |
Problem
tls: terminateis deprecated since OpenShell 0.0.24 (see policy schema docs). Keeping it generates WARN-level log entries on every sandbox start and can interfere with CONNECT tunnel handling in some proxy configurations.Reported in #1686. Also related to #1798 (CONNECT tunnel 403 for Brave/Slack on some setups).
Fix
Removed
tls: terminatefrom all affected policy files:nemoclaw-blueprint/policies/openclaw-sandbox.yaml— 12 instancespresets/brave.yaml,huggingface.yaml,jira.yaml,npm.yaml,outlook.yaml,pypi.yaml27 lines removed, no functional change (the field was ignored/deprecated).
Fixes #1686
Signed-off-by: Benedikt Schackenberg 6381261+BenediktSchackenberg@users.noreply.github.com
Summary by CodeRabbit