Feature: Allow to define a port range for custom_services about puppet-firewalld HOT 4 CLOSED

@gothicx How do you see this working? A separate entry for each member of the port range? A quick glance at http://www.firewalld.org/documentation/service/options.html doesn't show any native support for port ranges for custom services, unless I'm not seeing it...

from puppet-firewalld.

@crayfishx There is no official support, the idea is to have an entry in the port entry that provides a range and then the ruby code will parse that and transform into separated ports at service xml level.

You specify "port: 5000:5020", but in xml it will translate to one port per line. You see?

    <port protocol="tcp" port="5000" />
    <port protocol="tcp" port="5001" />
    <port protocol="tcp" port="5002" />
     ....

from puppet-firewalld.

The custom_service type already allows you to define multiple ports via a hash, so I guess we're not doing anything that different here, just allowing a short-hand expression in the way they are declared. This should be fairly easy to engineer.... Based on that, I think we can add this.

from puppet-firewalld.

Thanks :-)

from puppet-firewalld.