Skip to content

void platform install rejects existing Hyperdrive configurations backed by Workers VPC #834

Closed

Description

@max-voloshyn

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

  1. Create a Hyperdrive configuration for private PostgreSQL using a Workers VPC service.

  2. 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.

    void platform install --plan --hyperdrive "$HYPERDRIVE_ID"

Actual behavior

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.

Activity

  1. max-voloshyn commented on Nov 15, 2026

    @max-voloshyn
    ContributorAuthor

    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.

  2. added a commit that references this issue on Nov 16, 2026
    c807718
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions