Closed eseyman closed 5 months ago
Okay, started drafting a bit. I think you would like a variable such as nfsserver_exports_file
, with a default value of /etc/exports
. This would mean all defined shares will end up in that file.
Correct?
Correct?
It's a tad more complicated than that. In my mind, nfsserver_exports_file would be a per-share value (with /etc/exports being the default) and the role would manage all these files. This would allow you to put certain shares in /etc/exports.d/project1.exports, others in /etc/exports.d/project2.exports, ...).
Of course, this would only be possible on distributions that support /etc/exports.d/ and I'm not sure how many do (although it's a pretty safe bet that if Fedora supports it, RHEL supports it).
Describe the bug
I've started using this role to deploy my nfs-server but I want to group together exports in /etc/exports.d/*.exports The role only allows to deploy /etc/exports (the name is hardcoded in tasks/main.yml).
Playbook
Output
The role runs without errors but only deploys /etc/exports.
Environment