Skip to content

Commit 63ade5b

Browse files
docs: trim network reference bloat
1 parent 2e600c6 commit 63ade5b

1 file changed

Lines changed: 6 additions & 11 deletions

File tree

‎docs/src/content/docs/reference/network.md‎

Lines changed: 6 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,9 @@ If no `network:` permission is specified, it defaults to `network: defaults`, wh
1616

1717
Network permissions follow the principle of least privilege:
1818

19-
- **Default** (`network: defaults`): Basic infrastructure only
20-
- **Selective** (`network: { allowed: [...] }`): Only listed domains/ecosystems
21-
- **No access** (`network: {}`): All network blocked
19+
- **Default** (`network: defaults`) allows basic infrastructure only.
20+
- **Selective** (`network: { allowed: [...] }`) allows only the listed domains or ecosystems.
21+
- **No access** (`network: {}`) blocks all network access.
2222

2323
Listed domains automatically match all subdomains; wildcard patterns (`*.example.com`) are also supported — see [Wildcard Domain Patterns](#wildcard-domain-patterns).
2424

@@ -264,9 +264,9 @@ network:
264264

265265
## Troubleshooting
266266

267-
If you encounter network access blocked errors, verify that required domains or ecosystems are in the `allowed` list. Start with `network: defaults` and add specific requirements incrementally. Network access violations are logged in workflow execution logs.
267+
If network access is blocked, confirm the required domains or ecosystems are in `allowed`. Start with `network: defaults`, then add only what the workflow needs. Violations appear in workflow logs.
268268

269-
Use `gh aw logs --run-id <run-id>` to view firewall activity and identify blocked domains. For detailed diagnostics, use `gh aw audit <run-id>` — the **Firewall Analysis** section lists every domain request with its allow/deny status, request volume, and policy attribution. Pass two run IDs to compare firewall behavior between runs:
269+
Use `gh aw logs --run-id <run-id>` to identify blocked domains. For deeper analysis, run `gh aw audit <run-id>`; the **Firewall Analysis** section shows each domain request with its allow/deny status, request volume, and policy attribution. Pass two run IDs to compare runs:
270270

271271
```bash
272272
gh aw audit 12345678 # Single run
@@ -277,9 +277,4 @@ See the [Network Configuration Guide](/gh-aw/guides/network-configuration/#troub
277277

278278
## Related Documentation
279279

280-
- [Network Configuration Guide](/gh-aw/guides/network-configuration/) - Practical examples and common patterns
281-
- [Frontmatter](/gh-aw/reference/frontmatter/) - Complete frontmatter configuration guide
282-
- [Tools](/gh-aw/reference/tools/) - Tool-specific network access configuration
283-
- [Playwright](/gh-aw/reference/playwright/) - Browser automation and network requirements
284-
- [Audit Commands](/gh-aw/reference/audit/) - Firewall analysis and cross-run diff for understanding domain allow/block behavior
285-
- [Security Guide](/gh-aw/introduction/architecture/) - Comprehensive security guidance
280+
See also the [Network Configuration Guide](/gh-aw/guides/network-configuration/), [Frontmatter](/gh-aw/reference/frontmatter/), [Tools](/gh-aw/reference/tools/), [Playwright](/gh-aw/reference/playwright/), [Audit Commands](/gh-aw/reference/audit/), and the [Security Guide](/gh-aw/introduction/architecture/).

0 commit comments

Comments
 (0)