You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Void CLI 1.9.1 rejects an existing Hyperdrive configuration when its PostgreSQL origin is a Workers VPC service. The same parsing logic is present in the checked revision of upstream main.
Steps to reproduce
Create a Hyperdrive configuration for private PostgreSQL using a Workers VPC service.
In an interactive terminal, leave the VOID_PLATFORM_HYPERDRIVE_* selection variables unset and start a fresh install. Pass the Hyperdrive configuration ID and complete the prompts for the Cloudflare account that owns it.
The installer stops with platform: Cloudflare Hyperdrive config has an invalid origin port. Cloudflare returns origin.service_id and omits origin.host and origin.port for this origin type. Void checks the port before recognizing the Workers VPC origin. Cloudflare Hyperdrive API
Expected behavior
--hyperdrive <id> should recognize a Workers VPC origin and show the existing configuration as an adopted resource in the install plan, subject to the usual installation checks.
I opened #837 to support adopting an existing Workers VPC Hyperdrive with void platform install --hyperdrive <id>. The PR includes regression tests and the production verification results.
Activity
max-voloshyn commentedon Nov 15, 2026
I opened #837 to support adopting an existing Workers VPC Hyperdrive with
void platform install --hyperdrive <id>. The PR includes regression tests and the production verification results.Support Workers VPC Hyperdrive in platform installs (voidzero-dev#837)