Spike: outbound HTTPS from a Python component
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- infrastructure, networking, security
Research direction
Start with mise run setup-gh-sandbox and the gh sandbox networking work referenced in #46; inspect how DNS, certificates, and configuration are provided under the root mount. Compare the available wasi-sockets and wasi-http paths for the Python HTTP stack. Done means a Python component completes a verified HTTPS GET and the transport and certificate behavior is documented for #73.
Written by the indexing model from the issue text.
Description
The real blocker for any cloud CLI is outbound HTTPS, not Python. Prove a Python-lane component can make an HTTPS request end-to-end.
Scope
- Sockets/HTTP transport: wasi-sockets vs wasi-http — which does the host expose, and which does Python's
http.client/urllib3/requestsstack map onto cleanly? - TLS: where does cert verification happen (in-guest Python TLS vs host wasi-http)?
- DNS resolution + CA certificate bundle inside the sandbox.
- Reuse the
ghsandbox pattern (mise run setup-gh-sandbox— DNS/certs/config under a root mount).
Goal
A Python component performs GET https://… and gets a verified 200 through conch. Document the transport + cert story so awscli/gcloud spikes can build on it.
Shared dependency for #73 (awscli, gcloud). Relates to the gh networking work in #46.
- Dominant language
- Rust
- Stars
- 9
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from sd2k/conch
-
demo documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
enhancement gh-demo
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
enhancement gh-demo
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100