From 7d1b334bda6e17e4fdc91a9630a0204865e67d23 Mon Sep 17 00:00:00 2001 From: Elizabeth Engelman Date: Fri, 10 May 2019 09:35:44 -0500 Subject: [PATCH] Update postgraphile documentation to mention no-ignore-rbac flag --- documentation/postgraphile.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/documentation/postgraphile.md b/documentation/postgraphile.md index 8a77b8ce..06bf11ab 100644 --- a/documentation/postgraphile.md +++ b/documentation/postgraphile.md @@ -9,13 +9,14 @@ As of April 30, 2019, you can run Postgraphile pointed at the default `vulcanize ``` npm install -g postgraphile -postgraphile --connection postgres://localhost/vulcanize_public --schema=public,custom --disable-default-mutations +postgraphile --connection postgres://localhost/vulcanize_public --schema=public,custom --disable-default-mutations --no-ignore-rbac ``` Arguments: - `--connection` specifies the database. The above command connects to the default `vulcanize_public` database defined in [the example config](../staging/environments/public.toml.example). - `--schema` defines what schema(s) to expose. The above exposes the `public` schema (for core VulcanizeDB data) as well as a `custom` schema (where `custom` is the name of a schema defined in executed transformers). - `--disable-default-mutations` prevents Postgraphile from exposing create, update, and delete operations on your data, which are otherwise enabled by default. +- `--no-ignore-rbac` ensures that Postgraphile will only expose the tables, columns, fields, and query functions that the user has explicit access to. ## Customizing Postgraphile