agent-substrate / agent-substrate/substrate
Egress policies for raw-TCP traffic
- Dominant language
- Go
- Stars
- 1.9k
- Forks
- 317
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 289
Description
Decisions to be made:
- [ ] Should we allow Substrate admin to configure how raw-TCP egress traffic should be handled?
- [ ] Are there any needs to do credential injections for raw-TCP egress traffic?
Contributor guide
Research direction
No files or tests are referenced in the issue body. Start by finding where raw-TCP egress traffic is implemented and where admin policy configuration is parsed, then read nearby docs/comments to understand expected behavior. Check any existing egress/credential handling paths before proposing a decision. Done when the issue is converted into a concrete, actionable specification for admin-configurable raw-TCP policy and credential injection requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100