Yes , personally I'd prefer something like:
```
config_file_template
chroot_list_config_file_template
banned_email_config_file_template
```
rather than:
```
vsftpd_config_file_template
chroot_list_config_file_template
banned_email_config_file_template
``` 
my concern is that , under some points of view, this would break the "rule" expressed at the beginning:
"For each resource of a type that the module will manage, the preferred naming should be prefix_resource_namevar, unless there's only one resource of a type, where prefix_ can be dropped and resource_namevar can be used. "
unless we consider config_ as the prefix for the main config file and we are all happy with that 
Given this the above list could even become:
```
config_file_template
chroot_list_file_template
banned_email_file_template
```

Don't want to raise to many issues, but sooner or later some like these will arise when doing real modules.

(Incidentally I'd prefer a generic vsftpd::conf define to manage any additional file, rather than adding params to the main class for all the managed config files, but this is somehow a design choice that should not be faced by stdmod naming standars)