Minor improvements (#381)

* Minor improvements

* Document empty list vs null for users without privileges

* Change the wording for null values

* Add talk by Oleksii in Atmosphere
This commit is contained in:
zerg-junior
2018-11-06 11:08:13 +01:00
committed by GitHub
parent 86ba92ad02
commit ccaee94a35
11 changed files with 35 additions and 29 deletions
+3 -3
View File
@@ -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 `null` value it gets](https://kubernetes.io/docs/concepts/overview/object-management-kubectl/declarative-config/#how-apply-calculates-differences-and-merges-changes) (`foobar_user:` is equivalent to `foobar_user: null`).
The operator accepts the following options: `superuser`, `inherit`, `login`,
`nologin`, `createrole`, `createdb`, `replication`, `bypassrls`.