From fce75ca366f13959ef282a34eaf216d83adbb28f Mon Sep 17 00:00:00 2001 From: Sergey Dudoladov Date: Thu, 13 Sep 2018 16:33:33 +0200 Subject: [PATCH] Document empty list vs null for users without privileges --- docs/user.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/user.md b/docs/user.md index 523943446..61ed66ebb 100644 --- a/docs/user.md +++ b/docs/user.md @@ -20,7 +20,7 @@ spec: - createdb # role for application foo - foo_user: + foo_user: # or 'foo_user: []' #databases: name->owner databases: @@ -74,8 +74,8 @@ for an example of `zalando` role, defined with `superuser` and `createdb` flags. Manifest roles are defined as a dictionary, with a role name as a key and a -list of role options as a value. For a role without any options supply an empty -list. +list of role options as a value. For a role without any options it is best to supply the empty +list `[]`. It is also possible to leave this field empty as in our example manifests, but in certain cases such empty field may removed by Kubernetes [due to the implicit `null` value it gets](https://kubernetes.io/docs/concepts/overview/object-management-kubectl/declarative-config/#how-apply-calculates-differences-and-merges-changes). The operator accepts the following options: `superuser`, `inherit`, `login`, `nologin`, `createrole`, `createdb`, `replication`, `bypassrls`.