On Friday, 6 March 2015 23:16:26 UTC, ianm wrote:
There's a puppet-firewalld package in the Fedora and Epel repos
which installs Jiri Popelka's firewalld module.
That's the one I've been using up til now (installed using r10k rather than
an OS package) - the issue with that module is
On Sat, 7 Mar 2015, Nick Howes wrote:
Thanks Felix; all good points. I'll probably start off with define exec to
drive `firewall-cmd` then, and see how that turns out.
There's a puppet-firewalld package in the Fedora and Epel repos
which installs Jiri Popelka's firewalld module.
--
Ian
Hi Felix,
I'm aware there are no functions in the example, which would be implemented
either as a `define` in Puppet or as a custom type in Ruby - I was just
expressing that I'm open to any solution, which may involve some helper
function under the hood.
At the moment I'm using an existing
On 03/06/2015 04:12 PM, Nick Howes wrote:
I'm aware there are no functions in the example, which would be
implemented either as a `define` in Puppet or as a custom type in Ruby -
I was just expressing that I'm open to any solution, which may involve
some helper function under the hood.
That's
Thanks Felix; all good points. I'll probably start off with define exec
to drive `firewall-cmd` then, and see how that turns out.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails from it,
Hi,
there might be ways to achieve this, but also plenty caveats.
You mention all of functions, resources and providers, but I see no
indication that all of them relate to your question. Are you aware of
the differences between the three?
Have you implemented anything already, or are you still
Hello,
I am trying to define something that would let me do this, or something
like it:
fw_service { elasticsearch:
ports = [ '9200-9300' ],
zone = work,
}
fw_zone { work:
source_addresses = [ '10.0.0.0/16' ]
}
And for the fw_zone resource to be able to enumerate data
