More granular settings via "restrict" parameter

[nicwaller]

Current implementation of the restrict parameter only enables or disables restrictions on the server, but doesn't allow any customization beyond that.

Please consider either adding a parameter, or modifying the restrict parameter so that this module could be used to configure an NTP server for specific hosts or networks.

For example:

class { 'ntp':
  restrict => [
    'default kod nomodify notrap nopeer noquery',
    '192.168.0.0./16'
  ],
}

As it is right now, I need to provide my own template just to gain this functionality, so this module isn't very useful for me to set up NTP servers. This is especially problematic as I want to include the NTP module for all nodes, then customize accordingly with my hiera database.

[apenney]

Would #87 cover this for you?

[nicwaller]

@apenney From my brief read over your changeset, that looks exactly right.

Note, however, that this constitutes a change of the public API. If this project uses semantic versioning (http://semver.org/) then this patch will require a bump of the major version number. Otherwise, anybody who depends on the current behavior of $restrict will have problems after upgrading.

[apenney]

We're definitely semver'ing these. We're being fairly aggressive with ntp about adding new features and it's just gone through an enormous amount of change so I'm fine with just merging this and doing another release. Thanks for the feedback!