lib/docs/MEMBERS_DATABASE_METADATA_C...

29 lines
1.2 KiB
Markdown

# Members Database metadata client
Date: 2026-07-24
Provider source: Members commit
`6931b1177610a4bb41bf1bee488680b7146aa32b`.
The generated Members client exposes only:
- `GET /databases` with required `tenantId`;
- optional `databaseId`, `limit`, and `offset` filters;
- a dedicated `DatabaseMetadata` response model.
The provider requires compound API-key plus native member-session
authentication and exact `members:database:read` machine scope. Active tenant
members may read metadata; Contributors remain read-only.
`DatabaseMetadata` contains ID, TenantID, optional ClusterID, Active,
DatabaseName, Status, Type, CreatedDate, and LastModifiedDate. It has no DSN,
provisioning credential, processor token, password, or actor audit identity.
The generated Database client has no create, update, delete, provisioning,
generic-resource, Salesforce, sf-gate, or Cache operation.
The Ticket provider remains unavailable because its tenant/ownership,
decimal-money, inventory, and lifecycle contracts are not authoritative.
Database metadata is the safe DBMS discovery fallback and does not authorize
infrastructure writes. Production use remains blocked on a separately governed
exact-scope seed and provider release.