(MODULES-9656) - Enable using 0 for application pool settings

[pmcmaw]

Currently is it not possible to set the following to 0.

• cpu_limit
• max_processes
• restart_memory_limit
• restart_private_memory_limit
• restart_requests_limit

This PR adds a new property called whole number. A whole number can be any integer including 0 and applies it to the above.

[puppet-community-rangefinder]

iis_application_pool is a type

Breaking changes to this file WILL impact these 1 modules (exact match):

• tuto-chocolateyserver

Breaking changes to this file MAY impact these 1 modules (near match):

• example42-psick

This module is declared in 4 of 576 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[pmcmaw]

I have tested this change manually alongside the automated tests I have added.
I used the following manifest:

     iis_application_pool { 'this_pool':
        ensure                       => 'present',
        state                        => 'started',
        cpu_limit                    => '0',
        max_processes                => '0',
        restart_memory_limit         => '0',
        restart_private_memory_limit => '0',
        restart_requests_limit       => '0'
}

In the screenshot above you can see the values being set to 0 without any errors.

[michaeltlombardi]

lgtm!