postgresai 0.18.0-dev.14 → 0.18.0-dev.16
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/README.md +11 -6
- package/dist/bin/postgres-ai.js +607 -94
- package/dist/sql/01.role.sql +3 -3
- package/dist/sql/02.extensions.sql +1 -0
- package/dist/sql/03.permissions.sql +112 -8
- package/dist/sql/04.optional_rds.sql +1 -0
- package/dist/sql/05.optional_self_managed.sql +1 -0
- package/dist/sql/06.helpers.sql +1 -0
- package/dist/sql/uninit/01.helpers.sql +3 -1
- package/dist/sql/uninit/02.permissions.sql +14 -2
- package/dist/sql/uninit/03.role.sql +5 -4
- package/package.json +1 -1
- package/sql/01.role.sql +3 -3
- package/sql/02.extensions.sql +1 -0
- package/sql/03.permissions.sql +112 -8
- package/sql/04.optional_rds.sql +1 -0
- package/sql/05.optional_self_managed.sql +1 -0
- package/sql/06.helpers.sql +1 -0
- package/sql/uninit/01.helpers.sql +3 -1
- package/sql/uninit/02.permissions.sql +14 -2
- package/sql/uninit/03.role.sql +5 -4
package/README.md
CHANGED
|
@@ -216,12 +216,17 @@ and the result's `provider` remains `self-managed` for compatibility. It works w
|
|
|
216
216
|
PostgreSQL endpoint where the supplied user can create the monitoring role and grant privileges.
|
|
217
217
|
Use a direct endpoint, not a pooler.
|
|
218
218
|
|
|
219
|
-
The endpoint must be reachable from this machine, which prepares the database
|
|
220
|
-
|
|
221
|
-
|
|
222
|
-
|
|
223
|
-
|
|
224
|
-
|
|
219
|
+
The endpoint must be reachable from this machine, which prepares the database. The monitoring
|
|
220
|
+
box connects from its own static IP. When PostgresAI can't reach the database the way an IP
|
|
221
|
+
allowlist refuses (a timeout, a refused connection, no `pg_hba.conf` entry), deploy reserves the
|
|
222
|
+
box's IP before the box exists and stops at it: at a terminal it shows the IP and waits (Enter
|
|
223
|
+
continues, `s` stops); elsewhere it exits 3 with `"step":"allow_ip"` and `ip`, `cidr`, `host`,
|
|
224
|
+
`port`, `reserved_until`. Allow the IP on the database, then run `pgai mon deploy <url> --yes
|
|
225
|
+
--ip-allowed` to create the box with it. `--ip-first` asks for the IP first even when PostgresAI
|
|
226
|
+
can reach the database. A re-run never reserves a second IP; the IP is held 7 days and stays the
|
|
227
|
+
box's for its life. If the box still can't connect, it waits for up to 90 minutes, then is removed
|
|
228
|
+
and its IP kept: allow it, and run with `--ip-allowed` again. RDS can also use AWS PrivateLink,
|
|
229
|
+
and any database self-hosted monitoring (`--self-hosted`).
|
|
225
230
|
|
|
226
231
|
Without `--provider`, RDS hostnames still go to their console integration, and Supabase hostnames to the Supabase consent flow (`pgai mon deploy` for Supabase).
|
|
227
232
|
|