The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #13413

Firewall type should allow for cusom user rules.

Added by Trevor Vaughan over 2 years ago. Updated over 1 year ago.

Status:ClosedStart date:03/26/2012
Priority:NormalDue date:
Assignee:Ken Barber% Done:

0%

Category:firewallSpent time:-
Target version:-
Keywords: Branch:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.


Description

Understandably, not all firewall rules can be handled by the subset of options presented by the firewall types. Users should be able to define their own custom rules as necessary.

For instance:

firewall { '1234 do random stuff':
  custom => 'Some random ip6tables rules',
  provider => 'ip6tables'
}

History

#1 Updated by Jeff Weiss over 2 years ago

  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Ken Barber

#2 Updated by Ken Barber over 2 years ago

  • Project changed from Puppet Community Package Repository to Puppet Labs Modules

#3 Updated by Ken Barber over 2 years ago

  • Category set to firewall

#4 Updated by Ken Barber over 1 year ago

  • Status changed from Needs Decision to Closed

Hiya … I’ve fall behind a bit on all this work, also the bug tracker is moving to here: https://github.com/puppetlabs/puppet-firewall/issues I’ve managed to move what I still think is relevant and merge up items that are related. Consider this a slight declaration of ‘ticket debt’. If you think you’re issue isn’t represented in the new tracker feel free to open a new one.

Apologies for any confusion :–).

Ken.

#5 Updated by Ken Barber over 1 year ago

Sorry – the new URL is actually: http://github.com/puppetlabs/puppetlabs-firewall/issues … thanks @Wolfspyre.

Also available in: Atom PDF