Document empty list vs null for users without privileges
This commit is contained in:
		
							parent
							
								
									01704e3d66
								
							
						
					
					
						commit
						fce75ca366
					
				|  | @ -20,7 +20,7 @@ spec: | ||||||
|     - createdb |     - createdb | ||||||
| 
 | 
 | ||||||
|     # role for application foo |     # role for application foo | ||||||
|     foo_user: |     foo_user: # or 'foo_user: []' | ||||||
| 
 | 
 | ||||||
|   #databases: name->owner |   #databases: name->owner | ||||||
|   databases: |   databases: | ||||||
|  | @ -74,8 +74,8 @@ for an example of `zalando` role, defined with `superuser` and `createdb` | ||||||
| flags. | flags. | ||||||
| 
 | 
 | ||||||
| Manifest roles are defined as a dictionary, with a role name as a key and a | 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 of role options as a value. For a role without any options it is best to supply the empty | ||||||
| list. | 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`, | The operator accepts the following options:  `superuser`, `inherit`, `login`, | ||||||
| `nologin`, `createrole`, `createdb`, `replication`, `bypassrls`. | `nologin`, `createrole`, `createdb`, `replication`, `bypassrls`. | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue