You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The run parser and doc/run.md already expose and explain directional network policy, but the canonical CLI reference omitted those options. This adds the existing egress, ingress, host-loopback, proxy, and forwarding controls to doc/usage.md.
Live searches found no open issue or pull request for this omission. Recent documentation code-improvement proposals were merged, and no maintainer rejection covers this candidate.
Patch
Changed doc/usage.md.
Added 14 lines; deleted 0 lines; total changed lines: 14.
Made no dependency, public API/CLI/ABI, gitlink, or OpenVMM change.
Validation
python3 scripts/nvx.py run --help — passed; all documented options are present.
grep -E -- '--network-egress|--network-ingress|--host-loopback|--network-proxy' over the help output — passed.
Verified defaults and rule semantics against doc/run.md and scripts/nvx.py.
git diff --check — passed.
git diff --numstat — 14 0 doc/usage.md.
git diff --raw — one regular 100644 documentation file; no 160000 gitlink.
Clarify the behavior of the --network-ingress option in the portable profile.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Document required --network-egress for rule options
doc/usage.md:330
These rule options are rejected unless --network-egress is explicitly supplied, even though the preceding row lists an implicit allow default. Without documenting that requirement, the canonical reference leads to commands that fail with --network-egress is required (also described in doc/run.md:121-140).
This issue also appears on line 331 of the same file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scope
Category:
documentationThe
runparser anddoc/run.mdalready expose and explain directional network policy, but the canonical CLI reference omitted those options. This adds the existing egress, ingress, host-loopback, proxy, and forwarding controls todoc/usage.md.Live searches found no open issue or pull request for this omission. Recent documentation code-improvement proposals were merged, and no maintainer rejection covers this candidate.
Patch
doc/usage.md.Validation
python3 scripts/nvx.py run --help— passed; all documented options are present.grep -E -- '--network-egress|--network-ingress|--host-loopback|--network-proxy'over the help output — passed.doc/run.mdandscripts/nvx.py.git diff --check— passed.git diff --numstat—14 0 doc/usage.md.git diff --raw— one regular100644documentation file; no160000gitlink.