postgresai 0.18.0-dev.13 → 0.18.0-dev.15

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 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, and from
220
- PostgresAI. Before provisioning, PostgresAI tests the connection from its platform, whose
221
- address is not published, so the port must accept connections from the internet at that point.
222
- After provisioning, the monitoring server connects from its own IP address, shown on its page in
223
- the Console (Monitoring, then the instance). A database that must stay behind an IP allowlist
224
- needs AWS PrivateLink (RDS) or self-hosted monitoring (`--self-hosted`).
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
 
@@ -353,6 +358,11 @@ do `pgai dblab deploy` and `pgai dblab instances`:
353
358
  | `action_required` | do what `next` says, then re-run; also when the `--wait` of `pgai mon deploy` ran out with the box still starting (`next`: "Still in progress ... resume with pgai mon instances watch <id>") | 3 |
354
359
  | `failed` | `next` has the reason | 1 |
355
360
 
361
+ When PostgresAI is slow to answer the box request for a database URL, `pgai mon deploy` says it is still
362
+ creating the monitoring box and looks for the box for up to 5 minutes (30 seconds from the MCP tool)
363
+ before `--wait` starts, also with `--no-wait`; then it follows the box as usual. If no box appears, it
364
+ stops with `action_required` and says to check `pgai mon instances list` before running deploy again.
365
+
356
366
  `pgai init` exits with 130 when cancelled at a prompt (Ctrl-C, Ctrl-D).
357
367
 
358
368
  `--self-hosted` starts `mon local-install` with the monitoring URL, the API key and the ClickHouse