CLI mapping status¶
The sibling ACUGIS CLI registers a db Typer group from acugis.services.postgis. It currently exposes six commands, and every command calls not_implemented() without making a PostGIS Service request.
| CLI command | Intended API mapping | Current status |
|---|---|---|
acugis db list |
GET /api/databases |
Not implemented |
acugis db create |
POST /api/databases, then job polling |
Not implemented |
acugis db clone |
POST /api/databases/{id}/clone, then job polling |
Not implemented |
acugis db backup |
POST /api/databases/{id}/backup, then job polling |
Not implemented |
acugis db restore |
POST /api/databases/{id}/restore, then job polling |
Not implemented |
acugis db delete |
DELETE /api/databases/{id}, then job polling |
Not implemented |
The mapping column is documentation guidance inferred directly from the matching service routes and job behavior; it is not existing CLI behavior. No CLI commands exist for connection registry, PostgreSQL roles/groups, HBA rules, settings, uploads/imports, schema/table introspection, database access grants, jobs, or terminals.
The CLI can authenticate to Central with a saved cookie or a personal access token. However, PostGIS Service's auth provider currently validates Central session cookies only because it is not wired to a token store. A future CLI implementation cannot assume its PAT header will work directly against this service without corresponding service auth changes. No such changes are part of the current source.
Until implemented, use the HTTP API examples in Examples. Do not present the acugis db commands as operational automation.