I tried to find a solution for the exactly same problem, and it turned out it's best to take a slightly different approach.
Define home directory explicitly, for example:
user { $username:
comment => "comment",
home => "/home/${username}",
managehome => false,
# ...
}
When managehome
is false, the home directory is not even created. So you have to specifically define it. It's often best to make a custom definition for the whole user:
define custom_user($username, $password) {
user { $username:
home => "/home/${username}",
password => $password,
# etc.
}
file { "/home/${username}":
ensure => directory,
owner => $username,
require => User[$username],
# etc.
}
}
You can add more parameters, for example $keyvalue
, and create a keyfile if that parameter is given.
You can also define a global variable $home = "/home"
(OS specific, if needed) and get home dir with "${home}/${username}"
.
Edit: Using hash to define user-specific home directories
More recent Puppet versions (>= 2.6) support hashes. It would be possible to define a hash containing username => /path/to/home
mappings for each user:
$home = {
normal_user => '/home/normal_user',
backup => '/var/backup',
mysql => '/var/lib/mysql'
}
For any username, it is then easy to get home directory with $home['username']
.
Home directory hash with fallback
Most of the time, it would be best to have a "fallback default" if user does not exist in the hash. In theory this is possible, although syntax becomes a little cryptic and bloated:
$home = { ... }
$default_home = '/home'
user {$username:
home => has_key($home, $username) ? {
true => $home[$username],
false => "${default_home}/${username}"
}
# ...
}