Promote Database
Changed onPromote a Database into an OntologyEntity (creates the writeable surface).
ADMIN on the DATABASE being promoted, on top of the company-role gate. assert_can_write_entity only asks "is this caller owner or admin of the company" — it says nothing about the dataset — and PromoteDatabase auto-grants the promoter ADMIN on the new entity. Since row_policy.get_filters_for_entities skips a database's policies for anyone holding effective ADMIN on the entity, a company admin with no grant on D (or a deliberately row-restricted VIEWER on it) could promote D and read every row of the resulting E.
Requiring ADMIN on D first means the promoter already had that bypass — admin_db_ids would have exempted them from D's policies anyway — so promotion confers nothing new. That is the fix, rather than changing the entity-ADMIN bypass, which is a deliberate spec rule (§5.1) with other callers.
Request
- Base URLhttps://api.netter.ai (the document declares no server; this is the origin it was published from)
- URLhttps://api.netter.ai/api/v1/ontology/databases/{database_id}/promote
- Authnone declared
Path parameters
Request body
Response
Successful Response
Changes
- info
added the new optional request property
- info
- info
added the new optional request property
- info