- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with vas_local_user
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
This module allows you to manage both users and ssh_authorized_keys on systems using QAS/VAS. The thought behind it is make it easier for you to create users on systems with and without QAS installed.
This module manages one or more local users and ssh_authorized_keys (if configured). If it's a newly provisioned system it will create the user or users before installing QAS. If QAS is already installed on the system it will only manage the user and its ssh_authorized_keys if libuser is supported. The user will be managed on systems without QAS too.
- It affects the users and ssh_authorized_keys it's configured to manage.
If the module is included in the catalogue but not configured in any way it does not do anything. It takes in total four different parameters.
The following defaults are used when creating a user.
Not using QAS: 'manage_home' => true 'forcelocal' => true
Using QAS (settings above and...): 'before' => Class['vas']
Boolean to control if this module should manage users or not.
- Default: true
A hash of all users the module should manage/create.
- Default: undef
A hash of all ssh_authorized_keys the module should manage/create.
- Default: undef
Set to true to enable hiera_merge for parameter 'users'.
- Default: false
Set to true to enable hiera_merge for parameter 'groups'.
- Default: false
Classes:
- vas_local_user
This module uses before on Class['vas'] to guess whether QAS is in the catalogue or not. This module has been tested in combination with Ericsson/puppet-module-vas.
Requires Puppet >=3.2 since it uses User type's parameter forcelocal.
Please make changes atomic. Rebase your commits if neccessary to make it atomic.