Set up the proxy on a random port that's queryable from the control API
Metadata
Current evaluation
Feature request to allow proxy on random port with control API query endpoint. Unlabelled, no comments, inactive for 390 days.
Suggested action: needs triage
Reason: The issue has no labels, no maintainer comments, and no assignee, indicating it hasn't been assessed yet. While inactive for 390 days, the feature hasn't been implemented (NewHTTPProxy still requires a port parameter) and the project remains active, so it warrants triage rather than automatic closure.
Impact:
60
Quick Win:
30.0
Staleness:
75
Complexity:
50
Confidence:
60
Support Request:
10
Issue body
### What needs to get done
If the user doesn't pass a proxy port (or perhaps if the user explicitly passes `--random-proxy-port` or similar), set up the proxy on a random port.
The control API must have a way to query the proxy port.
### Why it needs to get done
Combined with https://github.com/canonical/fetch-service/issues/353 this removes the static nature of the ports, letting us control on a unix socket and proxy over any unused port. This makes it possible to run multiple crafts with `--enable-fetch-service` simultaneously (which is good because fetch service enabled builds are by their nature slow)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b |
Impact:
60
Quick Win:
30.0
Staleness:
75
Complexity:
50
Confidence:
60
Support Request:
10
|
needs triage | Feature request to allow proxy on random port with control API query endpoint. Unlabelled, no comments, inactive for 390 days. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/fetch-service#353
(confidence 80%)
Issue #353 (unix domain socket support) is referenced in the issue body as a combined improvement for port flexibility.
Related issues
No related issues found above the similarity threshold.