I don't know what would it lead to if I just edit the preceding comment, so I'll reformulate the rule here:

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 **the general** `resource_namevar` **must** be used.  In the former case, when using the real config file name as `prefix`, only the significant part of the name should be used, and any suffix it has must be dropped.

Examples:

Postfix:
master_config_file_template (using *master.cf* as prefix and dropping *.cf*)
main_config_file_template (using *main.cf* as prefix and dropping *.cf*)

Apache:
config_file_template (as there is a single *httpd.conf* file, the general form is used)

Vsftpd:
vsftpd_config_file_template
chroot_list_config_file_template
banned_email_config_file_template

Something like this looks better?