Accept wildcard inputs for noProxy
Open
area/cli
kind/enhancement
team/cli
- Dominant language
- Go
- Stars
- 2.1k
- Forks
- 328
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 9
Description
**What would you like to be added**:
Accept wildcard inputs for noProxy list
**Why is this needed**:
Wildcard inputs on noProxy do not get parsed properly when propagating to Etcdadm and Bottlerocket config.
Contributor guide
Research direction
Trace how the noProxy list is parsed before it is propagated to Etcdadm and Bottlerocket configuration. Compare the current handling with the wildcard-input requirement and verify that wildcard values survive both outputs; the issue names no files or tests, so those entry points must be located first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100