Go to file
Adrien "ze" Urban c128b1ea28 gid: default to "null"
using `|json` would let the state get an error if gid is a string, as it would
not be converted.

Using directly the `None` yaml value, and letting numbers as string be
converted by yaml parser.
2019-03-07 14:38:54 +01:00
users gid: default to "null" 2019-03-07 14:38:54 +01:00
LICENSE Removing extra new line characters 2015-05-07 13:39:04 -04:00
pillar.example group: add support for members 2019-03-07 12:03:30 +01:00
README.rst Dont force vim-formula on users 2018-06-15 14:27:14 +01:00

users

Formula to configure users via pillar.

Available states

users

Configures a user's home directory, group, the user itself, secondary groups, and associated keys. Also configures sudo access, and absent users.

users.sudo

Ensures the sudo group exists, the sudo package is installed and the sudo file is configured.

users.bashrc

Ensures the bashrc file exists in the users home directory. Sets 'manage_bashrc: True' in pillar per user. Defaults to False.

users.profile ----------------

Ensures the profile file exists in the users home directory. Sets 'manage_profile: True' in pillar per user. Defaults to False.

users.vimrc

Ensures the vimrc file exists in the users home directory. Sets 'manage_vimrc: True' in pillar per user. Defaults to False. This depends on the vim-formula being available and pillar users:use_vim_formula: True.

users.user_files ---------------

Permits the abitrary management of files. See pillar.example for configuration details.

Overriding default values

In order to separate actual user account definitions from configuration the pillar users-formula was introduced:

users:
  myuser:
    # stuff

users-formula:
  lookup:
    root_group: toor
    shell: '/bin/zsh'