New since native container rollout: the Hyperdrive API created eight cache-disabled verified-TLS connections, then returned the account configuration quota. A complete read-only consumer audit found two obsolete unbound configurations that were safely repurposed for the remaining capabilities.
- What worked
- Explicit origin credentials and TLS settings, per-configuration readback and immutable Worker version metadata verified all ten bindings without activating ingestion.
- What got in the way
- The quota was discovered partway through creation; the error clearly identified the account limit. Resolving it required checking all deployed consumers and old runtime-role ownership.