@the-meridian/cli 1.0.3 → 1.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +20 -0
- package/README.md +11 -0
- package/dist/index.js +1233 -100
- package/dist/index.js.map +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,25 @@
|
|
|
1
1
|
# @the-meridian/cli
|
|
2
2
|
|
|
3
|
+
## 1.2.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- fe0f470: `meridian dev` reaches your developer database through the Meridian database gateway with a certificate issued for you alone, where the environment uses the gateway. The CLI generates the key in memory, renews the certificate before it expires without dropping connections, and no longer needs to download cloud-sql-proxy there. `DATABASE_URL` keeps pointing at `127.0.0.1`, so your app and `prisma migrate dev` work unchanged.
|
|
8
|
+
|
|
9
|
+
### Patch Changes
|
|
10
|
+
|
|
11
|
+
- 5636813: When a Meridian environment does not offer developer databases, `meridian dev` now says so instead of suggesting a server failure to retry.
|
|
12
|
+
|
|
13
|
+
## 1.1.0
|
|
14
|
+
|
|
15
|
+
### Minor Changes
|
|
16
|
+
|
|
17
|
+
- ef6a53f: Add `meridian db credential list` and `meridian db credential revoke <credential>` for the credentials a backend running outside Meridian uses to reach a hosted environment's MySQL database through the Meridian database gateway. `list` shows each credential's label, MySQL user, access mode, status, last connection and certificate expiry; `revoke` drops a credential after asking (or with `--yes`), so a leaked one can be cut off from a terminal. Both take `--env <name>`. Creating and rotating credentials stay in the dashboard.
|
|
18
|
+
|
|
19
|
+
### Patch Changes
|
|
20
|
+
|
|
21
|
+
- be18bb6: The per-developer MySQL database is now called a **developer database** in every message and command description, matching the **Developer databases** page in the dashboard. Nothing about how it works changes.
|
|
22
|
+
|
|
3
23
|
## 1.0.3
|
|
4
24
|
|
|
5
25
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -98,6 +98,17 @@ Runs `npx prisma db seed` with the proxy up and `DATABASE_URL` set. Extra args:
|
|
|
98
98
|
|
|
99
99
|
Opens a SQL shell against the dev database: the real `mysql` client when it's on `PATH` (the password is passed via `MYSQL_PWD`, so it never appears in `ps`), otherwise a small built-in REPL over `mysql2`. `--repl` forces the built-in one, and `-e "SELECT 1"` runs a single statement and exits (`--json` formats the rows as JSON).
|
|
100
100
|
|
|
101
|
+
### `meridian db credential`
|
|
102
|
+
|
|
103
|
+
Lists and revokes credentials for reaching a hosted environment's MySQL database from a backend running outside Meridian, through the Meridian database gateway (mutual TLS plus a password). This acts on a hosted environment's database, not the developer database.
|
|
104
|
+
|
|
105
|
+
```bash
|
|
106
|
+
meridian db credential list --env production
|
|
107
|
+
meridian db credential revoke aws-backend --env production --yes
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
Creating and rotating credentials happen in the dashboard (Hosting > Database > External access), behind a browser session: a CLI token cannot issue database access. Revoking needs the Credentials: Manage permission on the app.
|
|
111
|
+
|
|
101
112
|
### Global flags
|
|
102
113
|
|
|
103
114
|
Accepted before or after the command name, so both `meridian --json whoami` and `meridian whoami --json` work.
|