mirrord-db-branching_skill

This skill helps you configure mirrord.json for safe database branching, generating valid configs and explaining copy modes, IAM auth, and branch management.

7

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill metalbear-co/skills --skill mirrord-db-branching

  • README.md2.0 KB
  • SKILL.md10.8 KB

Overview

This skill helps you generate, validate, and troubleshoot mirrord.json configurations for database branching. It focuses on MySQL and PostgreSQL setups, copy modes, IAM authentication, and branch lifecycle management so you can safely create isolated database copies for development and testing.

How this skill works

It inspects natural-language requests or user-provided JSON and produces minimal, schema-compliant db_branches entries. The skill validates generated or submitted configs against the authoritative db_branches JSON Schema and provides clear troubleshooting hints and next steps, including the mandatory mirrord verify-config command. It also explains copy modes, IAM options, and branch management commands.

When to use it

  • You need an isolated copy of a production DB for testing or migrations.
  • You want to configure MySQL or PostgreSQL branching with specific copy modes.
  • You must enable IAM authentication for Postgres (AWS RDS or GCP Cloud SQL).
  • You need help validating or fixing an existing mirrord.json db_branches entry.
  • You want guidance on Redis or MongoDB branching or local Redis runtime.

Best practices

  • Always use an environment variable for the app connection string and reference it in connection.url.variable.
  • Prefer copy.mode "empty" by default to keep branch creation fast and predictable.
  • Set id when you want branch reuse between sessions; check ttl_secs to avoid expiry surprises.
  • Run mirrord verify-config /path/to/config.json after any change.
  • Use schema-only or filtered copies instead of full copies for large databases to reduce setup time.

Example use cases

  • Create a MySQL branch for migration testing using copy.mode "schema" and your DATABASE_URL env var.
  • Set up a Postgres branch that uses AWS RDS IAM authentication and ensures AWS credentials are available in the pod.
  • Generate a filtered clone that copies only test users from a table for targeted integration tests.
  • Provision a local Redis branch for development using container runtime and REDIS_URL env var.
  • Validate and fix a supplied db_branches block to ensure correct types, required fields, and safe defaults.

FAQ

MySQL requires operator 3.129.0+, mirrord CLI 3.160.0+, and Helm chart operator.mysqlBranching: true. Postgres requires operator 3.131.0+, mirrord CLI 3.175.0+, and operator.pgBranching: true.

How do I ensure IAM auth works for GCP Cloud SQL?

GCP Cloud SQL requires TLS; include sslmode=require in the connection URL and supply GOOGLE_APPLICATION_CREDENTIALS or an override credentials_json / credentials_path.

What copy.mode should I choose to minimize setup time?

Use "empty" for fastest setup. Use "schema" when you need table structure but not data. Avoid "all" for large databases.

What single detail do you ask for if my request is underspecified?

I will ask for the database type, the environment variable name for the connection string, or the preferred copy mode—only one detail to proceed.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
mirrord-db-branching skill by metalbear-co/skills | VeilStrat