NFS and control file management
If applicable, this section should have a brief description of the technology the module integrates with and what that integration enables. This section should answer the questions: "What does this module do?" and "Why would I use it?"
If your module has a range of functionality (installation, configuration, management, etc.) this is the time to mention it.
- A list of files, packages, services, or operations that the module will alter, impact, or execute on the system it's installed on.
- This is a great place to stick any warnings.
- Can be in list or paragraph form.
This module requires pluginsync enabled
class { 'nfs':
is_server => true,
}
nfs::export { '/etc':
fsid => '1',
}
nfs::nfsmount { '/mnt/etc':
nfsdevice => '127.0.0.1:/etc',
}
Here, list the classes, types, providers, facts, etc contained in your module. This section should include all of the under-the-hood workings of your module so people know what the module is touching on their system but don't need to mess with things. (We are working on automating this section!)
This is where you list OS compatibility, version compatibility, etc.
We are pushing to have acceptance testing in place, so any new feature should have some test to check both presence and absence of any feature
- nfsmount:
- add attribute caching variables
- Fork it
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Added some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create new Pull Request