Skip to content

[Schema] Relocate HTTP proxy config to runtimeConfig.networkProxy per GA network spec #655

Description

@dhoehna

Description of the task

Follow-up from PR #634 (GA network policy schema migration for LXC/Bubblewrap), review thread #634 (comment).

PR #634 introduced the GA egress/ingress network schema but kept the HTTP proxy under network.proxy.http. Reviewer feedback (@SohamDas2021) notes the canonical GA network spec places the proxy in a top-level runtimeConfig.networkProxy (a URL), outside the network policy block.

Relocating the proxy was intentionally deferred out of PR #634 to keep that PR scoped to the network policy schema: introducing runtimeConfig is a new cross-cutting top-level config surface (schema, SDK public types, generated wire types, and every backend's proxy handling), which is meaningfully broader than a schema migration.

Expected outcome

  • Add a top-level runtimeConfig.networkProxy (URL) to the wire model (src/core/wxc_common/src/wire.rs); regenerate the dev JSON schema and SDK wire types via mxc_schema_gen (do not hand-edit generated artifacts).
  • Map it in config_parser.rs to the internal network_proxy model, defining precedence vs. the existing network.proxy.
  • Decide the deprecation/migration path for network.proxy.http (keep as an alias vs. remove before GA).
  • Update SDK public types (sdk/src/types.ts), the mxc-sdk policy port, and docs (docs/schema.md).
  • Confirm which backends honor the relocated proxy.

Additional context

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions