Add test for no_proxy defaulting
Open
Nobody has claimed this yet.
chore
priority/undecided
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
Originally posted by @cfryanr in https://github.com/vmware-tanzu/pinniped/pull/785#pullrequestreview-731986726
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced pull request and its review discussion to find the existing no_proxy behavior and relevant test location. Add coverage for the defaulting case, with done defined as the test passing and preserving the expected no_proxy default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100