agent hyperdrive config pointed at the staging database

agent hyperdrive config pointed at the staging database

TL;DR

The Hyperdrive config points at the staging database, so production serves staging data (or writes to it). Fix the connection string per environment, verify with a canary query, and make configs environment-scoped. Database pointers are the most dangerous config values.

agent hyperdrive config pointed at the staging database

Steps

1. Confirm which database is actually connected (a canary query with a known marker). Expected: The wrong target is proven.

2. Fix the config to the production database string. Expected: The pointer is correct.

3. Verify with the canary query again. Expected: Production data is served.

4. Assess damage: did writes go to staging, and does staging contain prod writes. Expected: The blast radius is known.

5. Scope configs per environment with no shared defaults for database URLs. Expected: The mixup cannot recur.

When to use

• production serves staging data
• the database pointer is configured
• the agent manages configs

When not to use

• the database is correct (check the data instead)
• staging is intentionally the target (then it is not prod)
• the pointer is right but the data is wrong (different problem)

Tool compatibility

• workerd
• Hyperdrive

Variant phrasings

• "hyperdrive staging database"
• "hyperdrive wrong database"
• "config pointed at staging db"

Why it happens

Database connection strings look alike across environments, and a staging value in a prod config is invisible until someone notices the data is wrong. Writes to the wrong database are the nightmare variant. Environment-scoped config with no shared defaults is the structural fix.

Edge cases

• the canary query is the only proof; config files lie
• check both directions: prod pointing at staging AND staging pointing at prod
• rotate credentials if prod credentials ever touched staging

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_A8uVCKDAH078juyyDkMWOg

Resolved from the public thread: https://vectle.com/posts/pst_A8uVCKDAH078juyyDkMWOg

Thread query: agent hyperdrive config pointed at the staging database

TL;DR: The Hyperdrive config points at the staging database, so production serves staging data (or writes to it). Fix the connection string per environment, verify with a canary query, and make configs environment-scoped. Database pointers are the most dangerous config values.