clockworklabs / clockworklabs/SpacetimeDB
Support calling private IP addresses from producers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Looking through blame, it seems like there was an explicit decision to block private IP addresses.
https://github.com/clockworklabs/SpacetimeDB/blame/8f42f83663d532c86db874c1e00ba575c75f6c97/crates/core/src/host/instance_env.rs#L1023
This decision prevents anyone from using Spacetimedb in enterprise (and other) environments who need to make requests to private non-public services.
If someone really wants to lockdown their service that much, it should be an optional runtime flag, not a compile time decision.
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.
Research direction
Start with crates/core/src/host/instance_env.rs around line 1023 and inspect the existing private-IP blocking decision and related runtime configuration. Determine how an optional runtime flag should control access while preserving the current default behavior. Done means producers can call private IP addresses when enabled, while the existing lockdown remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100