0data

dm

Minimal Deno CLI for managing a dev AWS RDS MySQL database.

Setup

Create the local config file:

deno task dm init

Edit:

~/.config/dm/config.json

Example:

{
  "defaultProfile": "default",
  "profiles": {
    "default": {
      "host": "your-dev-rds.xxxxxx.us-east-1.rds.amazonaws.com",
      "port": 3306,
      "user": "admin",
      "password": "dev-password",
      "database": "app_dev",
      "ssl": {
        "rejectUnauthorized": false
      }
    },
    "other_dev": {
      "host": "your-other-dev-rds.xxxxxx.us-east-1.rds.amazonaws.com",
      "port": 3306,
      "user": "admin",
      "password": "dev-password",
      "database": "other_app_dev",
      "ssl": {
        "rejectUnauthorized": false
      }
    }
  }
}

The init command sets the config directory to 700 and the config file to 600 on Linux.

For a dev RDS instance, "rejectUnauthorized": false is the quickest way to avoid local TLS CA setup. For a stronger setup, download the AWS RDS CA bundle and use:

{
  "ssl": {
    "caPath": "/path/to/global-bundle.pem",
    "rejectUnauthorized": true
  }
}

Commands

deno task dm ping
deno task dm databases
deno task dm tables
deno task dm profile ls
deno task dm profile current
deno task dm profile set default
deno task dm users
deno task dm describe users
deno task dm indexes users
deno task dm indexes users --format json
deno task dm count users
deno task dm bucket ls
deno task dm bucket set my-r2-bucket
deno task dm bucket files
deno task dm export
deno task dm export --prod
deno task dm export --prod --limit 5000

This first version runs with -A through the dm task.

count uses MySQL's information_schema.TABLES.TABLE_ROWS estimate. That is fast for large InnoDB tables, but it is approximate.

Ads exports are grouped by database profile. Samples live in exports/<profile>/sample/; production exports should go in exports/<profile>/production/ after the sample headers and values are approved. Use deno task dm export --prod to write plan exports to the production folder. Sample plan exports default to 100 rows, while --prod defaults to 1000 rows; pass --limit <n> to override either default.

The ads staging exports use the same dataset filenames in both folders: user_profiles.csv, contact_identifiers.csv, and purchase_events.csv. They are raw ClickHouse BI inputs, so nullable source values should be preserved in these files and filtered later in derived audience/upload tables.

Agents should generate exports/<current-profile>/export.config.json for repeatable ads exports. The plan contains table names, source-to-output column mappings, date columns, limits, and output filenames. Once the plan exists, run:

deno task dm export